Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a616b603b42bf40d477a6bfc9087140e184cfd0f634461930e40e0f3f2f9ddf4

Tx prefix hash: a0888fad83f48fb4a491140f208c4bbde3a5b92982aae9b96cc8a20f2117b1e9
Tx public key: c27ad249fda6acc2d245fceada94e5acf3831e2ac2071d6efbec76a6badc8de1
Timestamp: 1750815046 Timestamp [UCT]: 2025-06-25 01:30:46 Age [y:d:h:m:s]: 00:199:18:57:41
Block: 1312190 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 140818 RingCT/type: yes/0
Extra: 01c27ad249fda6acc2d245fceada94e5acf3831e2ac2071d6efbec76a6badc8de102110000000443846d66000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 39402542c64343b26b581297fee56b4add4146f5708cde6fd6a454db1ce366ca 0.600000000000 1799821 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": 1312200, "vin": [ { "gen": { "height": 1312190 } } ], "vout": [ { "amount": 600000000, "target": { "key": "39402542c64343b26b581297fee56b4add4146f5708cde6fd6a454db1ce366ca" } } ], "extra": [ 1, 194, 122, 210, 73, 253, 166, 172, 194, 210, 69, 252, 234, 218, 148, 229, 172, 243, 131, 30, 42, 194, 7, 29, 110, 251, 236, 118, 166, 186, 220, 141, 225, 2, 17, 0, 0, 0, 4, 67, 132, 109, 102, 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