Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: ddc6edadbf6e494514b6fcd6afe91f14918fda3099e15c0df54a79e4b279b58b

Tx prefix hash: 006272686fc93378c4d4ce6d2a5d4ae4f53e0fbc56a7d8b285af42516e0d6a85
Tx public key: c2f2bf764d7f3a5d5cda6650ec9a000b5197fef78d6ef9ec2423d0933e0c7927
Timestamp: 1649221234 Timestamp [UCT]: 2022-04-06 05:00:34 Age [y:d:h:m:s]: 03:024:22:31:59
Block: 474195 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 798270 RingCT/type: yes/0
Extra: 01c2f2bf764d7f3a5d5cda6650ec9a000b5197fef78d6ef9ec2423d0933e0c7927021100000005a272b9cb000000000000000000

1 output(s) for total of 16.473859610000 dcy

stealth address amount amount idx
00: e7eb9e9308e9e0e5b47adc81f4d56d7eb5f0f96c279ce65ac055aaf31ee1c930 16.473859610000 894190 of 0

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": 474205, "vin": [ { "gen": { "height": 474195 } } ], "vout": [ { "amount": 16473859610, "target": { "key": "e7eb9e9308e9e0e5b47adc81f4d56d7eb5f0f96c279ce65ac055aaf31ee1c930" } } ], "extra": [ 1, 194, 242, 191, 118, 77, 127, 58, 93, 92, 218, 102, 80, 236, 154, 0, 11, 81, 151, 254, 247, 141, 110, 249, 236, 36, 35, 208, 147, 62, 12, 121, 39, 2, 17, 0, 0, 0, 5, 162, 114, 185, 203, 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