Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 58979dafd31cee08871f119671c8487002a977a1ebb89e4c62a9c033106ec5f1

Tx prefix hash: 5581dad3504dc2d6c57ac299462bb72f51a72939f6bd9a0f9c34d116d9ea5c3f
Tx public key: bcf3ac5e8720031f9fef6e10f0b10d0289698b7fefe6a24ca7b459dc8896a84f
Timestamp: 1713116980 Timestamp [UCT]: 2024-04-14 17:49:40 Age [y:d:h:m:s]: 01:010:13:40:24
Block: 1000470 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 268532 RingCT/type: yes/0
Extra: 01bcf3ac5e8720031f9fef6e10f0b10d0289698b7fefe6a24ca7b459dc8896a84f02110000000159dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 712bc87ea9ddf6c784d0181ec0a27eb77ff28ac93095a6b85c594e32550555dc 0.600000000000 1460968 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": 1000480, "vin": [ { "gen": { "height": 1000470 } } ], "vout": [ { "amount": 600000000, "target": { "key": "712bc87ea9ddf6c784d0181ec0a27eb77ff28ac93095a6b85c594e32550555dc" } } ], "extra": [ 1, 188, 243, 172, 94, 135, 32, 3, 31, 159, 239, 110, 16, 240, 177, 13, 2, 137, 105, 139, 127, 239, 230, 162, 76, 167, 180, 89, 220, 136, 150, 168, 79, 2, 17, 0, 0, 0, 1, 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