Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 1c84ac984dbd16ffe96931e9c0bbde15031f4bb4b5eca773c39127a9f01510a5

Tx prefix hash: 9526326ca437706f69aa1005283121ec6b16b0287cd1945299158a56e1947aa3
Tx public key: 55e8e628cf2ea3e33486418b20f51be3ef37fa6ae71cb4d71cc5f8a135864be5
Timestamp: 1574090665 Timestamp [UCT]: 2019-11-18 15:24:25 Age [y:d:h:m:s]: 05:159:15:04:29
Block: 11559 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0986 kB
Tx version: 2 No of confirmations: 1257413 RingCT/type: yes/0
Extra: 0155e8e628cf2ea3e33486418b20f51be3ef37fa6ae71cb4d71cc5f8a135864be502110000000366a80d00000000000000000000

1 output(s) for total of 561.954461873000 dcy

stealth address amount amount idx
00: f2d02918ae8850df0b96234a71baff3edca89f707124df9a4cc618e9b759366f 561.954461873000 12636 of 0

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": 11569, "vin": [ { "gen": { "height": 11559 } } ], "vout": [ { "amount": 561954461873, "target": { "key": "f2d02918ae8850df0b96234a71baff3edca89f707124df9a4cc618e9b759366f" } } ], "extra": [ 1, 85, 232, 230, 40, 207, 46, 163, 227, 52, 134, 65, 139, 32, 245, 27, 227, 239, 55, 250, 106, 231, 28, 180, 215, 28, 197, 248, 161, 53, 134, 75, 229, 2, 17, 0, 0, 0, 3, 102, 168, 13, 0, 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