Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 552b1669e624819853cb8c739d98f6dbb6b69b7915f597a4bb6ac14d3ca174a9

Tx prefix hash: bc9e002a27707ba965a721f8f9f174b2d58ae7c1b3669318594c735dd18fd8d8
Tx public key: 6ca3c829851e857db018b6b881ae25db11b04180eea34f35a6049656e2965e2f
Timestamp: 1738436411 Timestamp [UCT]: 2025-02-01 19:00:11 Age [y:d:h:m:s]: 00:292:06:39:26
Block: 1209966 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 206652 RingCT/type: yes/0
Extra: 016ca3c829851e857db018b6b881ae25db11b04180eea34f35a6049656e2965e2f021100000003007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 0ed139c0daded8c37c702a900a76ad33c47dc884499c2de90c6a0d0754cb7de4 0.600000000000 1696713 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": 1209976, "vin": [ { "gen": { "height": 1209966 } } ], "vout": [ { "amount": 600000000, "target": { "key": "0ed139c0daded8c37c702a900a76ad33c47dc884499c2de90c6a0d0754cb7de4" } } ], "extra": [ 1, 108, 163, 200, 41, 133, 30, 133, 125, 176, 24, 182, 184, 129, 174, 37, 219, 17, 176, 65, 128, 238, 163, 79, 53, 166, 4, 150, 86, 226, 150, 94, 47, 2, 17, 0, 0, 0, 3, 0, 127, 151, 138, 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