Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: e9d6111e385895c1dda45c7a5e318ed3d520f3bcd12f6e7984aab2b24de74eee

Tx prefix hash: 53685832e9537f244f5ac7c06e4b4b178dad5799bddda5847ca42160e2a8a2d2
Tx public key: f4d8bc5865b528a0d048848d47e22dcafc2e3b6f9419abdf7fc634c5eb837cca
Timestamp: 1682371210 Timestamp [UCT]: 2023-04-24 21:20:10 Age [y:d:h:m:s]: 02:020:12:44:11
Block: 745839 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 536828 RingCT/type: yes/0
Extra: 01f4d8bc5865b528a0d048848d47e22dcafc2e3b6f9419abdf7fc634c5eb837cca021100000001b3164c24000000000000000000

1 output(s) for total of 2.073604801000 dcy

stealth address amount amount idx
00: 58fcafd04b95d420101f4f2e4554491ccd66807407804d40c35548d1d981575b 2.073604801000 1193326 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": 745849, "vin": [ { "gen": { "height": 745839 } } ], "vout": [ { "amount": 2073604801, "target": { "key": "58fcafd04b95d420101f4f2e4554491ccd66807407804d40c35548d1d981575b" } } ], "extra": [ 1, 244, 216, 188, 88, 101, 181, 40, 160, 208, 72, 132, 141, 71, 226, 45, 202, 252, 46, 59, 111, 148, 25, 171, 223, 127, 198, 52, 197, 235, 131, 124, 202, 2, 17, 0, 0, 0, 1, 179, 22, 76, 36, 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