Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 3cb20f67ef258431d8798c3d871fbec67e069ae803f4201e493641d4088e6b10

Tx prefix hash: cd0f01e1728902a2aa42b7fc7cfff96f53448dcbb954c206b422cafc1a0d65bb
Tx public key: f9e56b085633f2e1970790d255bf2ce2c3b25b228b98efe3ea3d2edbd2278896
Timestamp: 1706124752 Timestamp [UCT]: 2024-01-24 19:32:32 Age [y:d:h:m:s]: 01:076:17:05:09
Block: 942491 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 315931 RingCT/type: yes/0
Extra: 01f9e56b085633f2e1970790d255bf2ce2c3b25b228b98efe3ea3d2edbd22788960211000000047a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: b0349927c9138b73c685e0aff356c7b48ff95c5b1ab137c9b7c865635602d810 0.600000000000 1400663 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": 942501, "vin": [ { "gen": { "height": 942491 } } ], "vout": [ { "amount": 600000000, "target": { "key": "b0349927c9138b73c685e0aff356c7b48ff95c5b1ab137c9b7c865635602d810" } } ], "extra": [ 1, 249, 229, 107, 8, 86, 51, 242, 225, 151, 7, 144, 210, 85, 191, 44, 226, 195, 178, 91, 34, 139, 152, 239, 227, 234, 61, 46, 219, 210, 39, 136, 150, 2, 17, 0, 0, 0, 4, 122, 156, 244, 199, 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