Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 3f373a1f9b5018de7533ae75e2ef766de3ca3dd8c9d8c34a86a56350d32254dc

Tx prefix hash: d2c2a2eb141d61c6824c41ee6dfc83ea625bcf4868fcbbfb49e2838fc9784148
Tx public key: e8f63031d6fd096edbb9969b5cb5c1d5402983cc180a0fc5abdf8bf8c755800a
Timestamp: 1734580823 Timestamp [UCT]: 2024-12-19 04:00:23 Age [y:d:h:m:s]: 00:179:01:20:35
Block: 1178354 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 127674 RingCT/type: yes/0
Extra: 01e8f63031d6fd096edbb9969b5cb5c1d5402983cc180a0fc5abdf8bf8c755800a021100000009007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 4c11bc9e7f2e5dcbd35c4626b7d1213955c00d54277a1ccdca25172fb761a0c5 0.600000000000 1664741 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": 1178364, "vin": [ { "gen": { "height": 1178354 } } ], "vout": [ { "amount": 600000000, "target": { "key": "4c11bc9e7f2e5dcbd35c4626b7d1213955c00d54277a1ccdca25172fb761a0c5" } } ], "extra": [ 1, 232, 246, 48, 49, 214, 253, 9, 110, 219, 185, 150, 155, 92, 181, 193, 213, 64, 41, 131, 204, 24, 10, 15, 197, 171, 223, 139, 248, 199, 85, 128, 10, 2, 17, 0, 0, 0, 9, 0, 127, 151, 138, 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