Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 0b105162ce7f872dbdf44e6c56f07df4c718459b913c4c29db08802a9a618052

Tx prefix hash: 0503baa88d70aecceba66bb0ecfbb76ab066b80abd3187bb52475779360346ec
Tx public key: 4b7893884a1ddc66f85bf8c1dad4c1f3a3b12bcfd4ab340b06f5574865c987aa
Timestamp: 1710381800 Timestamp [UCT]: 2024-03-14 02:03:20 Age [y:d:h:m:s]: 00:346:14:37:46
Block: 977835 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 247787 RingCT/type: yes/0
Extra: 014b7893884a1ddc66f85bf8c1dad4c1f3a3b12bcfd4ab340b06f5574865c987aa0211000000067a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 4d2be98d97324e41daba4f89aeedd8f69473036b8dab7dc9a1205acf882ec2ff 0.600000000000 1437842 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": 977845, "vin": [ { "gen": { "height": 977835 } } ], "vout": [ { "amount": 600000000, "target": { "key": "4d2be98d97324e41daba4f89aeedd8f69473036b8dab7dc9a1205acf882ec2ff" } } ], "extra": [ 1, 75, 120, 147, 136, 74, 29, 220, 102, 248, 91, 248, 193, 218, 212, 193, 243, 163, 177, 43, 207, 212, 171, 52, 11, 6, 245, 87, 72, 101, 201, 135, 170, 2, 17, 0, 0, 0, 6, 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