Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 3ef0806a42178f72eec03beeffc443108a113e32d4934f82c99f775df963c1bd

Tx prefix hash: e988a3ca88876d03d3d3ff9b667fd11fa4e64482fc722352ead2945108ea656b
Tx public key: 1f12b1cff8051c30a05bff37d3382f7c2b128ba650e29b2a831fde724fbe7548
Timestamp: 1737312531 Timestamp [UCT]: 2025-01-19 18:48:51 Age [y:d:h:m:s]: 00:297:02:16:22
Block: 1200917 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 209847 RingCT/type: yes/0
Extra: 011f12b1cff8051c30a05bff37d3382f7c2b128ba650e29b2a831fde724fbe754802110000000225a35a0f000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 96a9ad4b15ba2e0db33a8312b8af3a78d0f458d745ec84dcbbef9cd4f5968bfb 0.600000000000 1687564 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": 1200927, "vin": [ { "gen": { "height": 1200917 } } ], "vout": [ { "amount": 600000000, "target": { "key": "96a9ad4b15ba2e0db33a8312b8af3a78d0f458d745ec84dcbbef9cd4f5968bfb" } } ], "extra": [ 1, 31, 18, 177, 207, 248, 5, 28, 48, 160, 91, 255, 55, 211, 56, 47, 124, 43, 18, 139, 166, 80, 226, 155, 42, 131, 31, 222, 114, 79, 190, 117, 72, 2, 17, 0, 0, 0, 2, 37, 163, 90, 15, 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