Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 2292aba1ded4cb33f81e36bbfeebf84fe488e0dcbaeaaf9d792c824a96d1d26f

Tx prefix hash: b2e02e4527786d1961feaf79169cb0cc5ace039d437c0a7a8f4c5959f648e838
Tx public key: 46588ff4c83e6bda4cba6ae8d8a51d78c2dc65f44c8a37cccb0b8f8633b1f93a
Timestamp: 1723321114 Timestamp [UCT]: 2024-08-10 20:18:34 Age [y:d:h:m:s]: 00:239:00:04:29
Block: 1085088 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 170689 RingCT/type: yes/0
Extra: 0146588ff4c83e6bda4cba6ae8d8a51d78c2dc65f44c8a37cccb0b8f8633b1f93a02110000000191e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 01efe052e5acbc298026cc1e16e298954f46c6d5de3c0d5542d1329bf24540e9 0.600000000000 1559587 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": 1085098, "vin": [ { "gen": { "height": 1085088 } } ], "vout": [ { "amount": 600000000, "target": { "key": "01efe052e5acbc298026cc1e16e298954f46c6d5de3c0d5542d1329bf24540e9" } } ], "extra": [ 1, 70, 88, 143, 244, 200, 62, 107, 218, 76, 186, 106, 232, 216, 165, 29, 120, 194, 220, 101, 244, 76, 138, 55, 204, 203, 11, 143, 134, 51, 177, 249, 58, 2, 17, 0, 0, 0, 1, 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