Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 5b44557be384246f13d89975753780a9dce2f9037096d6022b3e3cd3cb7c75c0

Tx prefix hash: fcd7fb594d513a738556343dece15053ee3f2923acd00b899d39a1348d38ca88
Tx public key: e83e8c1dcdc3ea8f5087d7983aec26560c5c5686c6c5b748b4f54d49b79fe109
Timestamp: 1722770454 Timestamp [UCT]: 2024-08-04 11:20:54 Age [y:d:h:m:s]: 00:172:07:28:30
Block: 1080523 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 123232 RingCT/type: yes/0
Extra: 01e83e8c1dcdc3ea8f5087d7983aec26560c5c5686c6c5b748b4f54d49b79fe109021100000005e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: f9adb20a991da3c66468faee6059496b9be33cc9190577950394518a72484b1b 0.600000000000 1553916 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": 1080533, "vin": [ { "gen": { "height": 1080523 } } ], "vout": [ { "amount": 600000000, "target": { "key": "f9adb20a991da3c66468faee6059496b9be33cc9190577950394518a72484b1b" } } ], "extra": [ 1, 232, 62, 140, 29, 205, 195, 234, 143, 80, 135, 215, 152, 58, 236, 38, 86, 12, 92, 86, 134, 198, 197, 183, 72, 180, 245, 77, 73, 183, 159, 225, 9, 2, 17, 0, 0, 0, 5, 233, 20, 221, 21, 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