Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 95fd45d6a675983e9aaeaaecd39cfcb9f50d5f13660aefc8d470b56794188f7c

Tx prefix hash: f0ba5ea7c86bc7fde103ee90d6f786a91892355faa910ee39064001be4d08601
Tx public key: 35904a822711fc0d6a61744dc65ae2f10a8dec92a7cf3c67c9d3a80fec0d0b27
Timestamp: 1639158608 Timestamp [UCT]: 2021-12-10 17:50:08 Age [y:d:h:m:s]: 02:343:15:43:29
Block: 392652 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 763652 RingCT/type: yes/0
Extra: 0135904a822711fc0d6a61744dc65ae2f10a8dec92a7cf3c67c9d3a80fec0d0b2702110000004f1cab2639000000000000000000

1 output(s) for total of 30.688897636000 dcy

stealth address amount amount idx
00: 14d779b752e41fe052f871cee1b7334e7e3c4b77e20ade1dbe12df20c15592c5 30.688897636000 789601 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": 392662, "vin": [ { "gen": { "height": 392652 } } ], "vout": [ { "amount": 30688897636, "target": { "key": "14d779b752e41fe052f871cee1b7334e7e3c4b77e20ade1dbe12df20c15592c5" } } ], "extra": [ 1, 53, 144, 74, 130, 39, 17, 252, 13, 106, 97, 116, 77, 198, 90, 226, 241, 10, 141, 236, 146, 167, 207, 60, 103, 201, 211, 168, 15, 236, 13, 11, 39, 2, 17, 0, 0, 0, 79, 28, 171, 38, 57, 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