Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 1889db58b99acd4433e24a8bf947069bf5180e4065a970a2832b6581d2d1b4f6

Tx prefix hash: 9829cccc8a7b65c92b9fdbeef59b65a8a5c4e5264002c87c25942736d99e01cf
Tx public key: 2032f35ec6a60f61d45a49ae153630ee26dd10f01e72f45cb99df5a7d493c13c
Timestamp: 1577440523 Timestamp [UCT]: 2019-12-27 09:55:23 Age [y:d:h:m:s]: 04:335:22:40:58
Block: 32793 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1129210 RingCT/type: yes/0
Extra: 012032f35ec6a60f61d45a49ae153630ee26dd10f01e72f45cb99df5a7d493c13c021100000034e39b962a000000000000000000

1 output(s) for total of 477.931729118000 dcy

stealth address amount amount idx
00: 53693c3a58a3c3c6b7c2c581f4f308d97c23c5b32cf297d5fe508275ba528bc7 477.931729118000 54617 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": 32803, "vin": [ { "gen": { "height": 32793 } } ], "vout": [ { "amount": 477931729118, "target": { "key": "53693c3a58a3c3c6b7c2c581f4f308d97c23c5b32cf297d5fe508275ba528bc7" } } ], "extra": [ 1, 32, 50, 243, 94, 198, 166, 15, 97, 212, 90, 73, 174, 21, 54, 48, 238, 38, 221, 16, 240, 30, 114, 244, 92, 185, 157, 245, 167, 212, 147, 193, 60, 2, 17, 0, 0, 0, 52, 227, 155, 150, 42, 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