Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: c2b377619ca41f987800fabea1c32bd3bb9f17bfd9ed983769b114393283b402

Tx prefix hash: dd811d613b16ef66a0e0cdf5d0dcb1c3f4c50a9f6db3e2e6a8bd4d60b586b3b6
Tx public key: 6bab11a07b631e3673d149431ad54d9b2b44fc1acd5ed91ffe13a9f600b0ebf1
Timestamp: 1735304542 Timestamp [UCT]: 2024-12-27 13:02:22 Age [y:d:h:m:s]: 00:170:00:02:31
Block: 1184305 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 121240 RingCT/type: yes/0
Extra: 016bab11a07b631e3673d149431ad54d9b2b44fc1acd5ed91ffe13a9f600b0ebf102110000000c1f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 5e2d48f7432018e319e5e5f714a0f9d07ed224cbb4a45c78633c59e4a3f3ac21 0.600000000000 1670762 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": 1184315, "vin": [ { "gen": { "height": 1184305 } } ], "vout": [ { "amount": 600000000, "target": { "key": "5e2d48f7432018e319e5e5f714a0f9d07ed224cbb4a45c78633c59e4a3f3ac21" } } ], "extra": [ 1, 107, 171, 17, 160, 123, 99, 30, 54, 115, 209, 73, 67, 26, 213, 77, 155, 43, 68, 252, 26, 205, 94, 217, 31, 254, 19, 169, 246, 0, 176, 235, 241, 2, 17, 0, 0, 0, 12, 31, 10, 83, 235, 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