Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: aaad420fb1078f0bedbd4c661f048be59954cb3332c58044fabbf29278178df2

Tx prefix hash: 0ceb57d60bc1aa1dcb51d6fbdf4b08c9850030168a63c4b7a9627e991040297f
Tx public key: 1090627b2e996aa5b4f7354f1048bdc6eb24db9214d6e3cdb98dc8551a8c482a
Timestamp: 1726439215 Timestamp [UCT]: 2024-09-15 22:26:55 Age [y:d:h:m:s]: 00:206:05:19:29
Block: 1110939 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 147221 RingCT/type: yes/0
Extra: 011090627b2e996aa5b4f7354f1048bdc6eb24db9214d6e3cdb98dc8551a8c482a02110000000291e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: fecb8314f03cb9b8ef1bfeed5a05cdbdabaab477d2ca36240203fda671d19bac 0.600000000000 1589724 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": 1110949, "vin": [ { "gen": { "height": 1110939 } } ], "vout": [ { "amount": 600000000, "target": { "key": "fecb8314f03cb9b8ef1bfeed5a05cdbdabaab477d2ca36240203fda671d19bac" } } ], "extra": [ 1, 16, 144, 98, 123, 46, 153, 106, 165, 180, 247, 53, 79, 16, 72, 189, 198, 235, 36, 219, 146, 20, 214, 227, 205, 185, 141, 200, 85, 26, 140, 72, 42, 2, 17, 0, 0, 0, 2, 145, 225, 60, 4, 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