Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 3ed63124e60ebd8f4fdbfa498570d3a89de9bd64eab828aa7c90e767af9cda88

Tx prefix hash: 79ab7caeedd29772f9695aab9d33c68a2366c585bdfcbd8225bde6fe258e0e17
Tx public key: 0b6c5145d8a56ee71e9a1bfc69424f8bd51a9e77748cb28a896959e432387c62
Timestamp: 1725735131 Timestamp [UCT]: 2024-09-07 18:52:11 Age [y:d:h:m:s]: 00:218:16:27:56
Block: 1105107 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 156142 RingCT/type: yes/0
Extra: 010b6c5145d8a56ee71e9a1bfc69424f8bd51a9e77748cb28a896959e432387c62021100000005e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 31a71a9ec2816d80c428abf073c8707bececf4a1050ecddab4781a9caa7feca5 0.600000000000 1582446 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": 1105117, "vin": [ { "gen": { "height": 1105107 } } ], "vout": [ { "amount": 600000000, "target": { "key": "31a71a9ec2816d80c428abf073c8707bececf4a1050ecddab4781a9caa7feca5" } } ], "extra": [ 1, 11, 108, 81, 69, 216, 165, 110, 231, 30, 154, 27, 252, 105, 66, 79, 139, 213, 26, 158, 119, 116, 140, 178, 138, 137, 105, 89, 228, 50, 56, 124, 98, 2, 17, 0, 0, 0, 5, 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