Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 932f44882bb344b17a1379121a2912cd60d677f1c55e5ae03e877a4fcdafa351

Tx prefix hash: 5cad9e52e41ea95fe9506c511c56c9357b2699725d5d8e8e736e5260ab4366d9
Tx public key: 05c0a526290cdf287d731d4752617c86402f28777df71faf79d31b85ef726f65
Timestamp: 1701118680 Timestamp [UCT]: 2023-11-27 20:58:00 Age [y:d:h:m:s]: 01:171:10:51:33
Block: 901020 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 383727 RingCT/type: yes/0
Extra: 0105c0a526290cdf287d731d4752617c86402f28777df71faf79d31b85ef726f6502110000000233af99f4000000000000000000

1 output(s) for total of 0.634668130000 dcy

stealth address amount amount idx
00: 3796c7e9e8f7096cf409bb8a92f9d9db1e32e2fc66fabcc94c65e20bd16964c9 0.634668130000 1357549 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": 901030, "vin": [ { "gen": { "height": 901020 } } ], "vout": [ { "amount": 634668130, "target": { "key": "3796c7e9e8f7096cf409bb8a92f9d9db1e32e2fc66fabcc94c65e20bd16964c9" } } ], "extra": [ 1, 5, 192, 165, 38, 41, 12, 223, 40, 125, 115, 29, 71, 82, 97, 124, 134, 64, 47, 40, 119, 125, 247, 31, 175, 121, 211, 27, 133, 239, 114, 111, 101, 2, 17, 0, 0, 0, 2, 51, 175, 153, 244, 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