Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 5b6dd5366fb643fa23062d76b34fde3e3dd350bc198c87151e7e7d14d6120a1f

Tx prefix hash: ada62a045ea387b99b2c5c931ebb03902a427b706853969f38c8f4afc4d5eabd
Tx public key: b996aa9ac706e5093fa92c6f5477dbcba8723748d639b5cb56fa33fe1c7f7722
Timestamp: 1583850481 Timestamp [UCT]: 2020-03-10 14:28:01 Age [y:d:h:m:s]: 05:061:21:47:20
Block: 79736 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1200127 RingCT/type: yes/0
Extra: 01b996aa9ac706e5093fa92c6f5477dbcba8723748d639b5cb56fa33fe1c7f77220211000000013b1b9791000000000000000000

1 output(s) for total of 334.042959210000 dcy

stealth address amount amount idx
00: f4b0eb9a085850d706997b9332e983b85a4a8d4a4aaf34447c4afca9f407c2fe 334.042959210000 145912 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": 79746, "vin": [ { "gen": { "height": 79736 } } ], "vout": [ { "amount": 334042959210, "target": { "key": "f4b0eb9a085850d706997b9332e983b85a4a8d4a4aaf34447c4afca9f407c2fe" } } ], "extra": [ 1, 185, 150, 170, 154, 199, 6, 229, 9, 63, 169, 44, 111, 84, 119, 219, 203, 168, 114, 55, 72, 214, 57, 181, 203, 86, 250, 51, 254, 28, 127, 119, 34, 2, 17, 0, 0, 0, 1, 59, 27, 151, 145, 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