Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 1f6e417d19de3f6c21ca4b4cb2fb61a2dfd74a87d172138690a129731247b79b

Tx prefix hash: 29ee374fe00851159975fb9231338037a559a9cf5363f84a7c96e1c2d5add314
Tx public key: ac2f5e700434e03bf9c69ccb460cc3af8b0a92347e9ceb7e1f3e9656414d90db
Timestamp: 1744048355 Timestamp [UCT]: 2025-04-07 17:52:35 Age [y:d:h:m:s]: 00:291:02:36:40
Block: 1256418 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 205701 RingCT/type: yes/0
Extra: 01ac2f5e700434e03bf9c69ccb460cc3af8b0a92347e9ceb7e1f3e9656414d90db0211000000046c98aa3d000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: c8208785419979a245ec6ae5bd32a3e78c999022503054234a1e2b78c503b9be 0.600000000000 1743531 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": 1256428, "vin": [ { "gen": { "height": 1256418 } } ], "vout": [ { "amount": 600000000, "target": { "key": "c8208785419979a245ec6ae5bd32a3e78c999022503054234a1e2b78c503b9be" } } ], "extra": [ 1, 172, 47, 94, 112, 4, 52, 224, 59, 249, 198, 156, 203, 70, 12, 195, 175, 139, 10, 146, 52, 126, 156, 235, 126, 31, 62, 150, 86, 65, 77, 144, 219, 2, 17, 0, 0, 0, 4, 108, 152, 170, 61, 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