Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 1db26f8c65a2260647b1a7cd64a87216eb389e0e9bd264d6a52dedc9f9819021

Tx prefix hash: b912ce8f81e66889aac8b6ec482438797cbd28c3df1fe8654c89087be83ef500
Tx public key: f3e58e737a40bf68a650629e79f2b5e5170812a0ca3a21e54715c5e916e0d925
Timestamp: 1710531087 Timestamp [UCT]: 2024-03-15 19:31:27 Age [y:d:h:m:s]: 01:061:02:57:18
Block: 979069 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 304668 RingCT/type: yes/0
Extra: 01f3e58e737a40bf68a650629e79f2b5e5170812a0ca3a21e54715c5e916e0d92502110000000259dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: ce74b97c7a4619a03680b71f14c871c8b25d2afce75a522620466e60ac793070 0.600000000000 1439100 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": 979079, "vin": [ { "gen": { "height": 979069 } } ], "vout": [ { "amount": 600000000, "target": { "key": "ce74b97c7a4619a03680b71f14c871c8b25d2afce75a522620466e60ac793070" } } ], "extra": [ 1, 243, 229, 142, 115, 122, 64, 191, 104, 166, 80, 98, 158, 121, 242, 181, 229, 23, 8, 18, 160, 202, 58, 33, 229, 71, 21, 197, 233, 22, 224, 217, 37, 2, 17, 0, 0, 0, 2, 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