Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: e25e0b5c72705ce4217ab8ba1ea284d4f20405a0f59010ca0d36c39454f19370

Tx prefix hash: 0d1ddf7e5559989bf337ed3d4fbc844e4ebf06119b807ffec7897737115b66e6
Tx public key: 6b9f6c0bdb18ced84dc68dc951af0e610f3e8b53fc345247e93422e8cbd430bc
Timestamp: 1711581395 Timestamp [UCT]: 2024-03-27 23:16:35 Age [y:d:h:m:s]: 00:308:06:02:12
Block: 987776 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 220358 RingCT/type: yes/0
Extra: 016b9f6c0bdb18ced84dc68dc951af0e610f3e8b53fc345247e93422e8cbd430bc0211000000010011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: c12366c0b2cce53c3582dee3c5cf1af07450d33fd7c037ac4eab524560d9abb7 0.600000000000 1448035 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": 987786, "vin": [ { "gen": { "height": 987776 } } ], "vout": [ { "amount": 600000000, "target": { "key": "c12366c0b2cce53c3582dee3c5cf1af07450d33fd7c037ac4eab524560d9abb7" } } ], "extra": [ 1, 107, 159, 108, 11, 219, 24, 206, 216, 77, 198, 141, 201, 81, 175, 14, 97, 15, 62, 139, 83, 252, 52, 82, 71, 233, 52, 34, 232, 203, 212, 48, 188, 2, 17, 0, 0, 0, 1, 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