Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b393d3df0bf56ef04c34225ee654a81d18d679e7f8802a32dd3e15439d37e312

Tx prefix hash: f0b89ab3bc8ea7ebaff8606078517d140b683bf179b72a6608384905f2f40424
Tx public key: 34956e5bb496e22b60c6e8343e271315dafbe5a94b151eaee478457e000ccb7f
Timestamp: 1701111169 Timestamp [UCT]: 2023-11-27 18:52:49 Age [y:d:h:m:s]: 01:170:17:24:59
Block: 900963 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 383197 RingCT/type: yes/0
Extra: 0134956e5bb496e22b60c6e8343e271315dafbe5a94b151eaee478457e000ccb7f02110000001275e3f0e9000000000000000000

1 output(s) for total of 0.634944193000 dcy

stealth address amount amount idx
00: afd22232c5021325e08027ec1a0d29b2bed603c925f5b6dd584b52bc32dd2a3c 0.634944193000 1357490 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": 900973, "vin": [ { "gen": { "height": 900963 } } ], "vout": [ { "amount": 634944193, "target": { "key": "afd22232c5021325e08027ec1a0d29b2bed603c925f5b6dd584b52bc32dd2a3c" } } ], "extra": [ 1, 52, 149, 110, 91, 180, 150, 226, 43, 96, 198, 232, 52, 62, 39, 19, 21, 218, 251, 229, 169, 75, 21, 30, 174, 228, 120, 69, 126, 0, 12, 203, 127, 2, 17, 0, 0, 0, 18, 117, 227, 240, 233, 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