Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f61c24f465b26ce4806b6e2d46b6b5b52667cdc65448fb35331220b66688ebde

Tx prefix hash: 4734b59e0e8b2fa151122c1dd09d7e27df9e03434f1ff64d922a71ebd5757c76
Tx public key: 76663b8f8ab8fcf5bf710d3896a39bfda0053fe6cb525dca5ea8f798f1ba60b9
Timestamp: 1744187444 Timestamp [UCT]: 2025-04-09 08:30:44 Age [y:d:h:m:s]: 00:032:08:50:12
Block: 1257581 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 23153 RingCT/type: yes/0
Extra: 0176663b8f8ab8fcf5bf710d3896a39bfda0053fe6cb525dca5ea8f798f1ba60b90211000000012609b3a0000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 0e4bd3bf848194f178b1ac0cc092bd85c30c3704feecb822372a21333dd4e421 0.600000000000 1744708 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": 1257591, "vin": [ { "gen": { "height": 1257581 } } ], "vout": [ { "amount": 600000000, "target": { "key": "0e4bd3bf848194f178b1ac0cc092bd85c30c3704feecb822372a21333dd4e421" } } ], "extra": [ 1, 118, 102, 59, 143, 138, 184, 252, 245, 191, 113, 13, 56, 150, 163, 155, 253, 160, 5, 63, 230, 203, 82, 93, 202, 94, 168, 247, 152, 241, 186, 96, 185, 2, 17, 0, 0, 0, 1, 38, 9, 179, 160, 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