Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 0c35af24142c80df95c1313e19b2d05dd5337d3e590b6bfb7d478080e4f25671

Tx prefix hash: a060d2dc095d5fb59f64f4a16e95f3af65b1904cf22d9812a1a74e1f09f474be
Tx public key: fe24644af12913bfb9285f4d1a4d134807dac52685ca13c0f3c2b9e9565d5e76
Timestamp: 1718598964 Timestamp [UCT]: 2024-06-17 04:36:04 Age [y:d:h:m:s]: 00:167:05:30:03
Block: 1045939 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 119697 RingCT/type: yes/0
Extra: 01fe24644af12913bfb9285f4d1a4d134807dac52685ca13c0f3c2b9e9565d5e760211000000020011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: b569db5c014f8c24431f364bbb99be4697ecf3098105797f0f821644c53ea526 0.600000000000 1515656 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": 1045949, "vin": [ { "gen": { "height": 1045939 } } ], "vout": [ { "amount": 600000000, "target": { "key": "b569db5c014f8c24431f364bbb99be4697ecf3098105797f0f821644c53ea526" } } ], "extra": [ 1, 254, 36, 100, 74, 241, 41, 19, 191, 185, 40, 95, 77, 26, 77, 19, 72, 7, 218, 197, 38, 133, 202, 19, 192, 243, 194, 185, 233, 86, 93, 94, 118, 2, 17, 0, 0, 0, 2, 0, 17, 5, 91, 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