Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a9682402d98204fffcbd0179cca4417329639ba2d0f8b73c8969f2bb82227ddc

Tx prefix hash: bf9953e593fee21e5a4f9c8df48c60267a86d9c9c88dcb9b1a6282ddff63349c
Tx public key: 4bf02a0725f4b55ff4519b37ac40cce3b68dacb41f04f24de810f087c7d4553e
Timestamp: 1704326560 Timestamp [UCT]: 2024-01-04 00:02:40 Age [y:d:h:m:s]: 01:083:13:29:16
Block: 927622 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 320803 RingCT/type: yes/0
Extra: 014bf02a0725f4b55ff4519b37ac40cce3b68dacb41f04f24de810f087c7d4553e02110000000252d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: a648cf4f5c598a29809e4fe0060c34a41e148e9374769dbe83d16837bbb3e872 0.600000000000 1385458 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": 927632, "vin": [ { "gen": { "height": 927622 } } ], "vout": [ { "amount": 600000000, "target": { "key": "a648cf4f5c598a29809e4fe0060c34a41e148e9374769dbe83d16837bbb3e872" } } ], "extra": [ 1, 75, 240, 42, 7, 37, 244, 181, 95, 244, 81, 155, 55, 172, 64, 204, 227, 182, 141, 172, 180, 31, 4, 242, 77, 232, 16, 240, 135, 199, 212, 85, 62, 2, 17, 0, 0, 0, 2, 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