Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 241507f839d0236bd10e64878e6fb01b8ba5c63a53fa039442e0c52289a10c38

Tx prefix hash: d8f9577651dba2535ac630f000c5d2a119f2682610693843e7d253e269f8b21b
Tx public key: 24916398ac32d7efe2635ddd5eb322decc405def6ee21003e4f09db4eb964c04
Timestamp: 1736181870 Timestamp [UCT]: 2025-01-06 16:44:30 Age [y:d:h:m:s]: 00:297:23:58:51
Block: 1191592 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 210464 RingCT/type: yes/0
Extra: 0124916398ac32d7efe2635ddd5eb322decc405def6ee21003e4f09db4eb964c0402110000000125a35a0f000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: abe2ccebf26f33fb21f8d3ad1cefcd7a14aea8aa0c08616e1bb6b9f79766243e 0.600000000000 1678131 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": 1191602, "vin": [ { "gen": { "height": 1191592 } } ], "vout": [ { "amount": 600000000, "target": { "key": "abe2ccebf26f33fb21f8d3ad1cefcd7a14aea8aa0c08616e1bb6b9f79766243e" } } ], "extra": [ 1, 36, 145, 99, 152, 172, 50, 215, 239, 226, 99, 93, 221, 94, 179, 34, 222, 204, 64, 93, 239, 110, 226, 16, 3, 228, 240, 157, 180, 235, 150, 76, 4, 2, 17, 0, 0, 0, 1, 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