Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 61371fd63db4ea8225b7f233f7e187bf6f6b6f87214a47298cec9c0f9ef4e63d

Tx prefix hash: 506dfbd991ea0b1c62bf34693da50ec0529320dcf09536147f5b689b5ed2af12
Tx public key: 8a4a3f0855f83ee376a1b39139bbd131aded2736ff41c0ebda07c00fa2e1b313
Timestamp: 1740899027 Timestamp [UCT]: 2025-03-02 07:03:47 Age [y:d:h:m:s]: 00:263:20:06:06
Block: 1230356 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 186306 RingCT/type: yes/0
Extra: 018a4a3f0855f83ee376a1b39139bbd131aded2736ff41c0ebda07c00fa2e1b3130211000000061f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: d1a42d3cdab5b363dd1d1ce66743f2c1d69128cf58b33822171e3f4c86895607 0.600000000000 1717253 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": 1230366, "vin": [ { "gen": { "height": 1230356 } } ], "vout": [ { "amount": 600000000, "target": { "key": "d1a42d3cdab5b363dd1d1ce66743f2c1d69128cf58b33822171e3f4c86895607" } } ], "extra": [ 1, 138, 74, 63, 8, 85, 248, 62, 227, 118, 161, 179, 145, 57, 187, 209, 49, 173, 237, 39, 54, 255, 65, 192, 235, 218, 7, 192, 15, 162, 225, 179, 19, 2, 17, 0, 0, 0, 6, 31, 10, 83, 235, 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