Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 5b0799e4b30f1deb97c6bfbb00a8c3da72a6db2513de085fdce2a7c8554cfd48

Tx prefix hash: 095212c797d92c542724f3c9aeea234368744b816158071d30d4c44b350de797
Tx public key: 7e015e81f1493fdb7a64f6f70487c6ef07b558b2eea9ec437f9ced6cb99dd6db
Timestamp: 1711544702 Timestamp [UCT]: 2024-03-27 13:05:02 Age [y:d:h:m:s]: 00:289:05:32:45
Block: 987479 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 207015 RingCT/type: yes/0
Extra: 017e015e81f1493fdb7a64f6f70487c6ef07b558b2eea9ec437f9ced6cb99dd6db0211000000020011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 4d43225d10a661c897ff8855fc89a320754b99e6b1ec5f486f634b44d4a4189e 0.600000000000 1447730 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": 987489, "vin": [ { "gen": { "height": 987479 } } ], "vout": [ { "amount": 600000000, "target": { "key": "4d43225d10a661c897ff8855fc89a320754b99e6b1ec5f486f634b44d4a4189e" } } ], "extra": [ 1, 126, 1, 94, 129, 241, 73, 63, 219, 122, 100, 246, 247, 4, 135, 198, 239, 7, 181, 88, 178, 238, 169, 236, 67, 127, 156, 237, 108, 185, 157, 214, 219, 2, 17, 0, 0, 0, 2, 0, 17, 5, 91, 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