Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f5ebf465b33a21f12f6154315388fa14975e98f666b781ed9d6a49a6224b76b1

Tx prefix hash: 04c6713d9f4569fadf108318a5a7ac30ebe696894b1dec585f0ad7bd7f843f12
Tx public key: 9e100be1f7d39b5978ac31b217ad1f8eba49a811bc0a449485c9e0ab40eeacb6
Timestamp: 1741247114 Timestamp [UCT]: 2025-03-06 07:45:14 Age [y:d:h:m:s]: 00:259:20:18:54
Block: 1233249 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 183443 RingCT/type: yes/0
Extra: 019e100be1f7d39b5978ac31b217ad1f8eba49a811bc0a449485c9e0ab40eeacb60211000000031f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: f2bef9d3302f5f857d3f85fbd2459418728e6cda51f5c9faf604f2545d23027d 0.600000000000 1720168 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": 1233259, "vin": [ { "gen": { "height": 1233249 } } ], "vout": [ { "amount": 600000000, "target": { "key": "f2bef9d3302f5f857d3f85fbd2459418728e6cda51f5c9faf604f2545d23027d" } } ], "extra": [ 1, 158, 16, 11, 225, 247, 211, 155, 89, 120, 172, 49, 178, 23, 173, 31, 142, 186, 73, 168, 17, 188, 10, 68, 148, 133, 201, 224, 171, 64, 238, 172, 182, 2, 17, 0, 0, 0, 3, 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