Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 40eaa096e7f52ca400f80017272248415aa2b9f656c31a24f3c3cd03cc3225a9

Tx prefix hash: 5cc6c1b4c00907451289b30562e302f241b73b21c064cb19d795be2bfa1c4745
Tx public key: 0efe652e38d4d47fdeea648d3df73f5c8ad08e865030ec9e2513453d7a67a7a8
Timestamp: 1748788287 Timestamp [UCT]: 2025-06-01 14:31:27 Age [y:d:h:m:s]: 00:172:08:50:45
Block: 1295686 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 120870 RingCT/type: yes/0
Extra: 010efe652e38d4d47fdeea648d3df73f5c8ad08e865030ec9e2513453d7a67a7a8021100000004bf51b2a2000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: b4aad047345b19daaa8daffe807a348fa16951a112f1386099bb10aaa2a8d417 0.600000000000 1783189 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": 1295696, "vin": [ { "gen": { "height": 1295686 } } ], "vout": [ { "amount": 600000000, "target": { "key": "b4aad047345b19daaa8daffe807a348fa16951a112f1386099bb10aaa2a8d417" } } ], "extra": [ 1, 14, 254, 101, 46, 56, 212, 212, 127, 222, 234, 100, 141, 61, 247, 63, 92, 138, 208, 142, 134, 80, 48, 236, 158, 37, 19, 69, 61, 122, 103, 167, 168, 2, 17, 0, 0, 0, 4, 191, 81, 178, 162, 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