Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 207e431b794fdc6cb563f92d04dd5d25c43dbcdc00decf8c7171499eb30eb33b

Tx prefix hash: e8e18348636b5c2dd7349a3635efb3c334f1f34109c596ff1ba161df5943e37a
Tx public key: e87b22569be3dc9f7f3607024c4d3361e520a01440f1cfb2701b6131fcf818ac
Timestamp: 1744756866 Timestamp [UCT]: 2025-04-15 22:41:06 Age [y:d:h:m:s]: 00:217:15:27:27
Block: 1262295 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 153275 RingCT/type: yes/0
Extra: 01e87b22569be3dc9f7f3607024c4d3361e520a01440f1cfb2701b6131fcf818ac0211000000026c98aa3d000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: a82c93a09cac7332b4669cb4ba4b4ab3d157c575c79f5faae1e302899f8d21e4 0.600000000000 1749472 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": 1262305, "vin": [ { "gen": { "height": 1262295 } } ], "vout": [ { "amount": 600000000, "target": { "key": "a82c93a09cac7332b4669cb4ba4b4ab3d157c575c79f5faae1e302899f8d21e4" } } ], "extra": [ 1, 232, 123, 34, 86, 155, 227, 220, 159, 127, 54, 7, 2, 76, 77, 51, 97, 229, 32, 160, 20, 64, 241, 207, 178, 112, 27, 97, 49, 252, 248, 24, 172, 2, 17, 0, 0, 0, 2, 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