Dinastycoin Blockchain Explorer

(no javascript - no cookies - no web analytics trackers - no images - open sourced)

Autorefresh is OFF

Tx hash: e21e4bffe70e859728d1bff6aca6b851de913e06e61730fcbc9d732bdb6cb335

Tx prefix hash: eb550d6298f1c8332091738e3c84da1db556a20c6a12f1215600e7a51a449b1c
Tx public key: b3d045361a3b389455c34108a254105bf85441adc25f8f20aaf9ede0b2778812
Timestamp: 1734406445 Timestamp [UCT]: 2024-12-17 03:34:05 Age [y:d:h:m:s]: 00:326:03:12:20
Block: 1176898 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 230579 RingCT/type: yes/0
Extra: 01b3d045361a3b389455c34108a254105bf85441adc25f8f20aaf9ede0b27788120211000000011f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 3dc8181a971238ad60f9b9fcd5de76f430dc40b0f47e8e0e74562a654ddc9b0b 0.600000000000 1663259 of 15

Check which outputs belong to given Dinastycoin address/subaddress and viewkey

For RingCT transactions, outputs' amounts are also decoded
Note: address/subaddress and viewkey are sent to the server, as the calculations are done on the server side



Prove to someone that you have sent them Dinastycoin in this transaction

Tx private key can be obtained using get_tx_key command in dinasty-wallet-cli command line tool
Note: address/subaddress and tx private key are sent to the server, as the calculations are done on the server side



{ "version": 2, "unlock_time": 1176908, "vin": [ { "gen": { "height": 1176898 } } ], "vout": [ { "amount": 600000000, "target": { "key": "3dc8181a971238ad60f9b9fcd5de76f430dc40b0f47e8e0e74562a654ddc9b0b" } } ], "extra": [ 1, 179, 208, 69, 54, 26, 59, 56, 148, 85, 195, 65, 8, 162, 84, 16, 91, 248, 84, 65, 173, 194, 95, 143, 32, 170, 249, 237, 224, 178, 119, 136, 18, 2, 17, 0, 0, 0, 1, 31, 10, 83, 235, 0, 0, 0, 0, 0, 0, 0, 0, 0 ], "rct_signatures": { "type": 0 } }


Less details
source code | explorer version (api): master-2022-04-20-3036769 (1.2) | dinastycoin version: 4.1-b41cfa2b8