Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 9fd0f88f42f6576720eca272431e8471f534f8fa0a628351a586630f6056ddb0

Tx prefix hash: 0c81a271564566f47072531c4864a584caae70e4cbf8ac7cf74e32d91abde4b7
Tx public key: fd0484eb5e6df52493c6393bf1747d26f8d9b4e48458338917c486e8e4d53a35
Timestamp: 1763517019 Timestamp [UCT]: 2025-11-19 01:50:19 Age [y:d:h:m:s]: 00:009:05:13:55
Block: 1415205 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 6600 RingCT/type: yes/0
Extra: 01fd0484eb5e6df52493c6393bf1747d26f8d9b4e48458338917c486e8e4d53a3502110000000134af31cc000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: b17425a0e1d1421ae2ae2f02647b01ce655cd5fe12ae6e83993797b25fe585cb 0.600000000000 1903702 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": 1415215, "vin": [ { "gen": { "height": 1415205 } } ], "vout": [ { "amount": 600000000, "target": { "key": "b17425a0e1d1421ae2ae2f02647b01ce655cd5fe12ae6e83993797b25fe585cb" } } ], "extra": [ 1, 253, 4, 132, 235, 94, 109, 245, 36, 147, 198, 57, 59, 241, 116, 125, 38, 248, 217, 180, 228, 132, 88, 51, 137, 23, 196, 134, 232, 228, 213, 58, 53, 2, 17, 0, 0, 0, 1, 52, 175, 49, 204, 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