Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b9cb8188766f59454b9d2b0de3ca21ea60d83859e93c8f36aa46dee0994f5536

Tx prefix hash: d78d33dfbce00de58d11bfbd3043f3d188aba8e6d50598497b3d35be817d89a8
Tx public key: a8467ad1bc93a28f26065cde695ee41f68b8f2f789f38f64c693be7cf129de8e
Timestamp: 1711387776 Timestamp [UCT]: 2024-03-25 17:29:36 Age [y:d:h:m:s]: 00:243:12:50:41
Block: 986179 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 174315 RingCT/type: yes/0
Extra: 01a8467ad1bc93a28f26065cde695ee41f68b8f2f789f38f64c693be7cf129de8e02110000000d52d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 286e7e570e0e7f9e3cd8773a25cd7d1ede786e1c3900995b13c4412d05420c17 0.600000000000 1446406 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": 986189, "vin": [ { "gen": { "height": 986179 } } ], "vout": [ { "amount": 600000000, "target": { "key": "286e7e570e0e7f9e3cd8773a25cd7d1ede786e1c3900995b13c4412d05420c17" } } ], "extra": [ 1, 168, 70, 122, 209, 188, 147, 162, 143, 38, 6, 92, 222, 105, 94, 228, 31, 104, 184, 242, 247, 137, 243, 143, 100, 198, 147, 190, 124, 241, 41, 222, 142, 2, 17, 0, 0, 0, 13, 82, 212, 126, 148, 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