Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 9bf5f33b4bc4e4423199da4940ca472fea9b195c463854086d54846aa119d1a4

Tx prefix hash: f300a4e80fc8c176f92e68681fdef43b61c84dea2cfcfe9a0bd04cb213b43365
Tx public key: a061bfb00b75a1c029d06cc310f6df31c658cdfb598d6edc9defbeb5e8624104
Timestamp: 1697348005 Timestamp [UCT]: 2023-10-15 05:33:25 Age [y:d:h:m:s]: 01:140:22:11:29
Block: 869960 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 361728 RingCT/type: yes/0
Extra: 01a061bfb00b75a1c029d06cc310f6df31c658cdfb598d6edc9defbeb5e86241040211000000024b8f5122000000000000000000

1 output(s) for total of 0.804380270000 dcy

stealth address amount amount idx
00: 9d3095ff2018437a96acf5340ad664d82f60e732e73b72af2ef4e3e89e48640e 0.804380270000 1324825 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": 869970, "vin": [ { "gen": { "height": 869960 } } ], "vout": [ { "amount": 804380270, "target": { "key": "9d3095ff2018437a96acf5340ad664d82f60e732e73b72af2ef4e3e89e48640e" } } ], "extra": [ 1, 160, 97, 191, 176, 11, 117, 161, 192, 41, 208, 108, 195, 16, 246, 223, 49, 198, 88, 205, 251, 89, 141, 110, 220, 157, 239, 190, 181, 232, 98, 65, 4, 2, 17, 0, 0, 0, 2, 75, 143, 81, 34, 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