Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: dc754106d2dbe09904ad309a49e833aff00a6ffbc962405b7a4bc067ec3dfd62

Tx prefix hash: 2aca49d66a6d01f7a9ff4c7dd364ae94ff2235eb12f156ef05deb033677b3263
Tx public key: f2add4168a72f7fad0e851c3fb81193b75b7b6e504dae204b9fb7ce7ef397e12
Timestamp: 1727169673 Timestamp [UCT]: 2024-09-24 09:21:13 Age [y:d:h:m:s]: 00:227:00:22:02
Block: 1116993 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 162084 RingCT/type: yes/0
Extra: 01f2add4168a72f7fad0e851c3fb81193b75b7b6e504dae204b9fb7ce7ef397e12021100000001e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 516f556b9047ae4cb251bf83aa4ed1bba1c35a421e53e153ba674c676092a0c0 0.600000000000 1597672 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": 1117003, "vin": [ { "gen": { "height": 1116993 } } ], "vout": [ { "amount": 600000000, "target": { "key": "516f556b9047ae4cb251bf83aa4ed1bba1c35a421e53e153ba674c676092a0c0" } } ], "extra": [ 1, 242, 173, 212, 22, 138, 114, 247, 250, 208, 232, 81, 195, 251, 129, 25, 59, 117, 183, 182, 229, 4, 218, 226, 4, 185, 251, 124, 231, 239, 57, 126, 18, 2, 17, 0, 0, 0, 1, 233, 20, 221, 21, 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