Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 3c75e46b128fbf4bf98ec305ac845a6332d11593107c89e398745a2b5cdf86c5

Tx prefix hash: 6fd1930344a0ab2d6e96fa2ea6b7c428aa0aaae2af4bd74739776e3543cfd83e
Tx public key: cf0b6da661585dc35272e8bac5f4e3c2ccb99590eeec761bb287cd183f952f5d
Timestamp: 1734994820 Timestamp [UCT]: 2024-12-23 23:00:20 Age [y:d:h:m:s]: 00:092:13:32:20
Block: 1181765 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 65913 RingCT/type: yes/0
Extra: 01cf0b6da661585dc35272e8bac5f4e3c2ccb99590eeec761bb287cd183f952f5d0211000000031f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 3b71017d5001bcbf1572f47e305ad180d9441cab60550ae5b375e4f1257adc30 0.600000000000 1668190 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": 1181775, "vin": [ { "gen": { "height": 1181765 } } ], "vout": [ { "amount": 600000000, "target": { "key": "3b71017d5001bcbf1572f47e305ad180d9441cab60550ae5b375e4f1257adc30" } } ], "extra": [ 1, 207, 11, 109, 166, 97, 88, 93, 195, 82, 114, 232, 186, 197, 244, 227, 194, 204, 185, 149, 144, 238, 236, 118, 27, 178, 135, 205, 24, 63, 149, 47, 93, 2, 17, 0, 0, 0, 3, 31, 10, 83, 235, 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