Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 7a9c43441da79bff267e72d2e1fd22b75bcc7116c68ea458e4ddfb05f81bbf8b

Tx prefix hash: bff6d37224b1ed20434ce37704a97ec9a288c266392b046e2622ae2d5115f3c1
Tx public key: cdba524b4c4aed478572d34424cf67887bf6a0d92b8d3f6c8223954fc27a0f26
Timestamp: 1730764369 Timestamp [UCT]: 2024-11-04 23:52:49 Age [y:d:h:m:s]: 00:172:13:13:56
Block: 1146704 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 123180 RingCT/type: yes/0
Extra: 01cdba524b4c4aed478572d34424cf67887bf6a0d92b8d3f6c8223954fc27a0f26021100000005007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 36d803566c691cf098da9477a394e104e6adb28b0dfe0834f2e229879df3afab 0.600000000000 1631395 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": 1146714, "vin": [ { "gen": { "height": 1146704 } } ], "vout": [ { "amount": 600000000, "target": { "key": "36d803566c691cf098da9477a394e104e6adb28b0dfe0834f2e229879df3afab" } } ], "extra": [ 1, 205, 186, 82, 75, 76, 74, 237, 71, 133, 114, 211, 68, 36, 207, 103, 136, 123, 246, 160, 217, 43, 141, 63, 108, 130, 35, 149, 79, 194, 122, 15, 38, 2, 17, 0, 0, 0, 5, 0, 127, 151, 138, 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