Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: c574337765875ac739137848a0f7d3d267c4e71073740db0d0310b99b1b5ee21

Tx prefix hash: 5b2252222cb0780acf8c610ee11fb595956de4ce255a53e84f9324f11051a532
Tx public key: de61e04137dcdf7e99e472906eb9dbd5e1ae3f26fb01916085a648b5c63b04c3
Timestamp: 1712537474 Timestamp [UCT]: 2024-04-08 00:51:14 Age [y:d:h:m:s]: 01:219:18:59:16
Block: 995661 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 415777 RingCT/type: yes/0
Extra: 01de61e04137dcdf7e99e472906eb9dbd5e1ae3f26fb01916085a648b5c63b04c30211000000020011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 82508a9feff179d5565c8967f0c47ab017f6cec8a04302c535817719645c6c9f 0.600000000000 1456075 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": 995671, "vin": [ { "gen": { "height": 995661 } } ], "vout": [ { "amount": 600000000, "target": { "key": "82508a9feff179d5565c8967f0c47ab017f6cec8a04302c535817719645c6c9f" } } ], "extra": [ 1, 222, 97, 224, 65, 55, 220, 223, 126, 153, 228, 114, 144, 110, 185, 219, 213, 225, 174, 63, 38, 251, 1, 145, 96, 133, 166, 72, 181, 198, 59, 4, 195, 2, 17, 0, 0, 0, 2, 0, 17, 5, 91, 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