Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 1985aafc9730fd3811ec178093895be4a37b7f50db6e71d26c83f0b2c3c24a07

Tx prefix hash: df633293b0c43d490f131209d0ae01b37c83a17b00216ef1dbbe458072d80f7d
Tx public key: 906f56cf3308f83f4bd50804ef0bb4b8c5163a0acd280c4313a477f8865b87f2
Timestamp: 1731956118 Timestamp [UCT]: 2024-11-18 18:55:18 Age [y:d:h:m:s]: 00:209:14:56:44
Block: 1156575 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 149586 RingCT/type: yes/0
Extra: 01906f56cf3308f83f4bd50804ef0bb4b8c5163a0acd280c4313a477f8865b87f20211000000011f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 8a018c1f88c8a0768ef755489064a2cc9e95857b668e81c3c0424a87281aeeba 0.600000000000 1642198 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": 1156585, "vin": [ { "gen": { "height": 1156575 } } ], "vout": [ { "amount": 600000000, "target": { "key": "8a018c1f88c8a0768ef755489064a2cc9e95857b668e81c3c0424a87281aeeba" } } ], "extra": [ 1, 144, 111, 86, 207, 51, 8, 248, 63, 75, 213, 8, 4, 239, 11, 180, 184, 197, 22, 58, 10, 205, 40, 12, 67, 19, 164, 119, 248, 134, 91, 135, 242, 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