Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: d52a6a5ba2444a9319ad1b29414204dfaa7a281fc9dd36c4c2f55a7601b97c87

Tx prefix hash: ae2b3874e308884a95677b44a150d3f69dad4b38bf1b73ed6a357e65dad84a28
Tx public key: 52aa66c5c8600124deb5bd3e17667397f313bcc2bcc1c78e571e5b326270ecd8
Timestamp: 1744782488 Timestamp [UCT]: 2025-04-16 05:48:08 Age [y:d:h:m:s]: 00:207:13:07:45
Block: 1262506 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 146049 RingCT/type: yes/0
Extra: 0152aa66c5c8600124deb5bd3e17667397f313bcc2bcc1c78e571e5b326270ecd80211000000056c98aa3d000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: e918e2fff186357a56dfa8516ad5cfed9c2d18aa95e7af597391e643b31b2fd6 0.600000000000 1749685 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": 1262516, "vin": [ { "gen": { "height": 1262506 } } ], "vout": [ { "amount": 600000000, "target": { "key": "e918e2fff186357a56dfa8516ad5cfed9c2d18aa95e7af597391e643b31b2fd6" } } ], "extra": [ 1, 82, 170, 102, 197, 200, 96, 1, 36, 222, 181, 189, 62, 23, 102, 115, 151, 243, 19, 188, 194, 188, 193, 199, 142, 87, 30, 91, 50, 98, 112, 236, 216, 2, 17, 0, 0, 0, 5, 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