Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 405b5ef4b1118913b40f6711da821aee60b09674cbdb39985ea82866b4016865

Tx prefix hash: 25ff2e59e957ae51d465aba5d9b16f9309b02cf7ddcd719428326f09431ab34f
Tx public key: e97f7c91c20a6ee60a93837498fe9f0e0e86ce076b406f019cf41b8f4ba94405
Timestamp: 1730490747 Timestamp [UCT]: 2024-11-01 19:52:27 Age [y:d:h:m:s]: 00:138:00:50:19
Block: 1144433 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 98519 RingCT/type: yes/0
Extra: 01e97f7c91c20a6ee60a93837498fe9f0e0e86ce076b406f019cf41b8f4ba94405021100000002007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: d5b9a5278b20085bf09d0618416c1e291a0b12a7f2c7425354d92f3dc51f72b5 0.600000000000 1628654 of 15

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": 1144443, "vin": [ { "gen": { "height": 1144433 } } ], "vout": [ { "amount": 600000000, "target": { "key": "d5b9a5278b20085bf09d0618416c1e291a0b12a7f2c7425354d92f3dc51f72b5" } } ], "extra": [ 1, 233, 127, 124, 145, 194, 10, 110, 230, 10, 147, 131, 116, 152, 254, 159, 14, 14, 134, 206, 7, 107, 64, 111, 1, 156, 244, 27, 143, 75, 169, 68, 5, 2, 17, 0, 0, 0, 2, 0, 127, 151, 138, 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