Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 0689761a17bc12079e3249e60ff7438113e495d7e5adbc8e0ed65ed921f77a96

Tx prefix hash: 230d22ecf90e8e3dd8c814904ee7356618bf514dca420e84ea8cba27ea97a4cb
Tx public key: aeddf09fb68140cb0cc241a65ef53c466a05781c2a430b3b2820aabda6816a7e
Timestamp: 1693578023 Timestamp [UCT]: 2023-09-01 14:20:23 Age [y:d:h:m:s]: 01:075:23:33:55
Block: 838682 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 315601 RingCT/type: yes/0
Extra: 01aeddf09fb68140cb0cc241a65ef53c466a05781c2a430b3b2820aabda6816a7e021100000003faf35c9c000000000000000000

1 output(s) for total of 1.021170955000 dcy

stealth address amount amount idx
00: bf3128ae32ad089ad616e7d926e379b0d85c337eea7786f3ca8f0449dd59c832 1.021170955000 1291452 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": 838692, "vin": [ { "gen": { "height": 838682 } } ], "vout": [ { "amount": 1021170955, "target": { "key": "bf3128ae32ad089ad616e7d926e379b0d85c337eea7786f3ca8f0449dd59c832" } } ], "extra": [ 1, 174, 221, 240, 159, 182, 129, 64, 203, 12, 194, 65, 166, 94, 245, 60, 70, 106, 5, 120, 28, 42, 67, 11, 59, 40, 32, 170, 189, 166, 129, 106, 126, 2, 17, 0, 0, 0, 3, 250, 243, 92, 156, 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