Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 0c6652f917deb298bafc96324ce246819e93929685532c8e5b2a4343858dc70f

Tx prefix hash: caf46f0984d9b2e48643563cfdf4a45bbd69b049aaff95219712b94c16ef5f6a
Tx public key: 7468ff4ee73a8f00d027c244578a30e152c771362b9acdfd8107f45cf210f8c9
Timestamp: 1710248944 Timestamp [UCT]: 2024-03-12 13:09:04 Age [y:d:h:m:s]: 01:050:11:19:33
Block: 976729 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 297066 RingCT/type: yes/0
Extra: 017468ff4ee73a8f00d027c244578a30e152c771362b9acdfd8107f45cf210f8c902110000000252d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 80ca7a74b1b67f44ee1b4c3f791ab72c0a5d6950a1a398dabda196dcda77118e 0.600000000000 1436724 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": 976739, "vin": [ { "gen": { "height": 976729 } } ], "vout": [ { "amount": 600000000, "target": { "key": "80ca7a74b1b67f44ee1b4c3f791ab72c0a5d6950a1a398dabda196dcda77118e" } } ], "extra": [ 1, 116, 104, 255, 78, 231, 58, 143, 0, 208, 39, 194, 68, 87, 138, 48, 225, 82, 199, 113, 54, 43, 154, 205, 253, 129, 7, 244, 92, 242, 16, 248, 201, 2, 17, 0, 0, 0, 2, 82, 212, 126, 148, 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