Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b96a660ba361c809891b9be9fc2f8cef34218e7e44f4210d354e4db041ec4225

Tx prefix hash: 359943eb9daca910b836de95bc267ece91c2cdd0426bacd4367ed350fc298dcd
Tx public key: fa0742ed13e3a81a6c41e8f302ed76318f890dd22177b6a9365acc6f7aeb49c4
Timestamp: 1577256445 Timestamp [UCT]: 2019-12-25 06:47:25 Age [y:d:h:m:s]: 05:070:17:27:14
Block: 31213 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1200375 RingCT/type: yes/0
Extra: 01fa0742ed13e3a81a6c41e8f302ed76318f890dd22177b6a9365acc6f7aeb49c40211000000018a2ee0d9000000000000000000

1 output(s) for total of 483.703505002000 dcy

stealth address amount amount idx
00: 1c1bfa0c8d6f341b2799ded7baba89caec7c115e3edf4eadc455d47e29783056 483.703505002000 51607 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": 31223, "vin": [ { "gen": { "height": 31213 } } ], "vout": [ { "amount": 483703505002, "target": { "key": "1c1bfa0c8d6f341b2799ded7baba89caec7c115e3edf4eadc455d47e29783056" } } ], "extra": [ 1, 250, 7, 66, 237, 19, 227, 168, 26, 108, 65, 232, 243, 2, 237, 118, 49, 143, 137, 13, 210, 33, 119, 182, 169, 54, 90, 204, 111, 122, 235, 73, 196, 2, 17, 0, 0, 0, 1, 138, 46, 224, 217, 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