Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 21333678879d5e6a36311008a7563e7f66206bab386cb3c8976994e5c427b922

Tx prefix hash: c15b9d312d6bd51332e2991e7c541a2e21f135f1264a63f0e9eed531417935f3
Tx public key: 411cddc9aac3e53ac58ed0c16d848b616ab033902a0336b2558fe0f80740a524
Timestamp: 1729391325 Timestamp [UCT]: 2024-10-20 02:28:45 Age [y:d:h:m:s]: 00:196:03:58:45
Block: 1135403 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 140000 RingCT/type: yes/0
Extra: 01411cddc9aac3e53ac58ed0c16d848b616ab033902a0336b2558fe0f80740a524021100000003007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: eb01cd3783620f1bfbf9223aee7e24f843725fc9e3d5e79d7b5bf5dcb1e86e5f 0.600000000000 1618740 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": 1135413, "vin": [ { "gen": { "height": 1135403 } } ], "vout": [ { "amount": 600000000, "target": { "key": "eb01cd3783620f1bfbf9223aee7e24f843725fc9e3d5e79d7b5bf5dcb1e86e5f" } } ], "extra": [ 1, 65, 28, 221, 201, 170, 195, 229, 58, 197, 142, 208, 193, 109, 132, 139, 97, 106, 176, 51, 144, 42, 3, 54, 178, 85, 143, 224, 248, 7, 64, 165, 36, 2, 17, 0, 0, 0, 3, 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