Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 6b53f60b382410b9761b61818e19ff0a436db11bff521cdff2fcb9961872a2ea

Tx prefix hash: cfda53f0c7201e18ac1c610c5352494ebeb4a2530cb243677fd629d9f730ebb4
Tx public key: 3488a71c3baa4f63db6820c30822fc89df39a15056671702f1a145b77f3afa5f
Timestamp: 1710692649 Timestamp [UCT]: 2024-03-17 16:24:09 Age [y:d:h:m:s]: 01:037:21:52:14
Block: 980412 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 288076 RingCT/type: yes/0
Extra: 013488a71c3baa4f63db6820c30822fc89df39a15056671702f1a145b77f3afa5f0211000000027a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 979a26a5e8a6d5093dd4b17f4e7a0da8369e4329f637785df6ebd0c64855a709 0.600000000000 1440477 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": 980422, "vin": [ { "gen": { "height": 980412 } } ], "vout": [ { "amount": 600000000, "target": { "key": "979a26a5e8a6d5093dd4b17f4e7a0da8369e4329f637785df6ebd0c64855a709" } } ], "extra": [ 1, 52, 136, 167, 28, 59, 170, 79, 99, 219, 104, 32, 195, 8, 34, 252, 137, 223, 57, 161, 80, 86, 103, 23, 2, 241, 161, 69, 183, 127, 58, 250, 95, 2, 17, 0, 0, 0, 2, 122, 156, 244, 199, 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