Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 9d0569f00a0126d332dc69c0965b873c147ccf48543ed35028c8f9abf8225ea9

Tx prefix hash: 7f3d428d55efbfbfe1817708d70ed826cff900c0af05400f47a867b36bb6df30
Tx public key: 6654f12ce337d36572d4be071b0dca1ce4aa101014dfdd8b4f1780363b4dfd56
Timestamp: 1695602022 Timestamp [UCT]: 2023-09-25 00:33:42 Age [y:d:h:m:s]: 01:115:14:44:01
Block: 855479 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 343909 RingCT/type: yes/0
Extra: 016654f12ce337d36572d4be071b0dca1ce4aa101014dfdd8b4f1780363b4dfd5602110000000275e3f0e9000000000000000000

1 output(s) for total of 0.898344670000 dcy

stealth address amount amount idx
00: 8bee11e1f7a5f7e7878ffa30e1538d6f189bbfced6a158ef733b1e8be68532ba 0.898344670000 1309503 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": 855489, "vin": [ { "gen": { "height": 855479 } } ], "vout": [ { "amount": 898344670, "target": { "key": "8bee11e1f7a5f7e7878ffa30e1538d6f189bbfced6a158ef733b1e8be68532ba" } } ], "extra": [ 1, 102, 84, 241, 44, 227, 55, 211, 101, 114, 212, 190, 7, 27, 13, 202, 28, 228, 170, 16, 16, 20, 223, 221, 139, 79, 23, 128, 54, 59, 77, 253, 86, 2, 17, 0, 0, 0, 2, 117, 227, 240, 233, 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