Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 9d2843c6a319057ddb9d8a6dc3e0ae57e5723408432804a418d94c2117eeeca6

Tx prefix hash: 09eafb8f48a75533625109705905e07997eb1d837e8976d73fa8ac45b81b024d
Tx public key: 3ef6c563dfd7380838efdd26f3a5f9afd47146ca29ad14a16a2fded00c4bf6d6
Timestamp: 1745875968 Timestamp [UCT]: 2025-04-28 21:32:48 Age [y:d:h:m:s]: 00:040:10:51:24
Block: 1271570 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 28935 RingCT/type: yes/0
Extra: 013ef6c563dfd7380838efdd26f3a5f9afd47146ca29ad14a16a2fded00c4bf6d602110000000325a35a0f000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 223b9a67108dc8449cc96b2023db83d284228b18b54e9702c1411d91b001796f 0.600000000000 1758833 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": 1271580, "vin": [ { "gen": { "height": 1271570 } } ], "vout": [ { "amount": 600000000, "target": { "key": "223b9a67108dc8449cc96b2023db83d284228b18b54e9702c1411d91b001796f" } } ], "extra": [ 1, 62, 246, 197, 99, 223, 215, 56, 8, 56, 239, 221, 38, 243, 165, 249, 175, 212, 113, 70, 202, 41, 173, 20, 161, 106, 47, 222, 208, 12, 75, 246, 214, 2, 17, 0, 0, 0, 3, 37, 163, 90, 15, 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