Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: aeceeff5acd70ef697db76418d5dd2acf48a4a3a5db20a404db47423fe3f21e9

Tx prefix hash: f9caa6992075d0ec99ba2c24690c3c930817b3dfd1453145436e3b2fd55c393d
Tx public key: e5250f31d3b9b16f8e9639f9a7e922ad93259493aa4140111d6fb290d8429ce3
Timestamp: 1713069900 Timestamp [UCT]: 2024-04-14 04:45:00 Age [y:d:h:m:s]: 01:203:20:25:32
Block: 1000080 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 404370 RingCT/type: yes/0
Extra: 01e5250f31d3b9b16f8e9639f9a7e922ad93259493aa4140111d6fb290d8429ce302110000000359dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: af76ea86d4dda45ab1d2002419564c81ed5537d04dcd01637c523e9b0f0fc534 0.600000000000 1460570 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": 1000090, "vin": [ { "gen": { "height": 1000080 } } ], "vout": [ { "amount": 600000000, "target": { "key": "af76ea86d4dda45ab1d2002419564c81ed5537d04dcd01637c523e9b0f0fc534" } } ], "extra": [ 1, 229, 37, 15, 49, 211, 185, 177, 111, 142, 150, 57, 249, 167, 233, 34, 173, 147, 37, 148, 147, 170, 65, 64, 17, 29, 111, 178, 144, 216, 66, 156, 227, 2, 17, 0, 0, 0, 3, 89, 218, 211, 245, 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