Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 6ff6aa02fce7c87050d4ecf5d44ace072f0889bd0218d92e1c1102b530215243

Tx prefix hash: 4985253efae83b2c2d18485d7ecdc1e44177cdd7f7b4c35dcfa78f912c9495d5
Tx public key: fbcbd7980a3f1711802e1403dc57e4f63ae21f152b6a83a150d205180e0ab68f
Timestamp: 1723449610 Timestamp [UCT]: 2024-08-12 08:00:10 Age [y:d:h:m:s]: 00:242:16:19:44
Block: 1086154 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 173335 RingCT/type: yes/0
Extra: 01fbcbd7980a3f1711802e1403dc57e4f63ae21f152b6a83a150d205180e0ab68f02110000000391e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: bce13249d71fde75513d532a4572edf1a6cdafe6e151ba689cecbce2a4f44e9d 0.600000000000 1560747 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": 1086164, "vin": [ { "gen": { "height": 1086154 } } ], "vout": [ { "amount": 600000000, "target": { "key": "bce13249d71fde75513d532a4572edf1a6cdafe6e151ba689cecbce2a4f44e9d" } } ], "extra": [ 1, 251, 203, 215, 152, 10, 63, 23, 17, 128, 46, 20, 3, 220, 87, 228, 246, 58, 226, 31, 21, 43, 106, 131, 161, 80, 210, 5, 24, 14, 10, 182, 143, 2, 17, 0, 0, 0, 3, 145, 225, 60, 4, 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