Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b11cbd7f9c061e2b3a00246b2588e8bd58d698db868e4b84575d1345665e0cda

Tx prefix hash: 57a0bf3015d04b0a62a20f3447faf563d953316777b4dcaccf56c9155d70c277
Tx public key: 7b98e7ae79d40164cdfe9debc0b826173b0a65638f67d4fe69bfbd2dee863f4f
Timestamp: 1703171311 Timestamp [UCT]: 2023-12-21 15:08:31 Age [y:d:h:m:s]: 01:084:15:38:12
Block: 918035 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 321637 RingCT/type: yes/0
Extra: 017b98e7ae79d40164cdfe9debc0b826173b0a65638f67d4fe69bfbd2dee863f4f0211000000080011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: f46f06e57ceb07f70adbbeffaf182dd5d0233dd11c5c701470f3151f06072a4f 0.600000000000 1375671 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": 918045, "vin": [ { "gen": { "height": 918035 } } ], "vout": [ { "amount": 600000000, "target": { "key": "f46f06e57ceb07f70adbbeffaf182dd5d0233dd11c5c701470f3151f06072a4f" } } ], "extra": [ 1, 123, 152, 231, 174, 121, 212, 1, 100, 205, 254, 157, 235, 192, 184, 38, 23, 59, 10, 101, 99, 143, 103, 212, 254, 105, 191, 189, 45, 238, 134, 63, 79, 2, 17, 0, 0, 0, 8, 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