Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f2ac817185072e8a51509ef47d87a4b14f145b7f4b3c870e7dd84cc168319c66

Tx prefix hash: a7882feeb265e1d4eaf9b805e21fced5da3e2a6a4d95b6ce6f84f61abc732394
Tx public key: a8be7c8a04f319a1dbac6348840835d4962de317f0d0142cfb53a1adcf4b83ea
Timestamp: 1711688123 Timestamp [UCT]: 2024-03-29 04:55:23 Age [y:d:h:m:s]: 01:047:01:45:20
Block: 988656 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 294632 RingCT/type: yes/0
Extra: 01a8be7c8a04f319a1dbac6348840835d4962de317f0d0142cfb53a1adcf4b83ea0211000000027a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 2b93bf4d405fc86fe6d7e2761b6b85f2c81fdcc0e266de03b82f0c655aa73b3b 0.600000000000 1448937 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": 988666, "vin": [ { "gen": { "height": 988656 } } ], "vout": [ { "amount": 600000000, "target": { "key": "2b93bf4d405fc86fe6d7e2761b6b85f2c81fdcc0e266de03b82f0c655aa73b3b" } } ], "extra": [ 1, 168, 190, 124, 138, 4, 243, 25, 161, 219, 172, 99, 72, 132, 8, 53, 212, 150, 45, 227, 23, 240, 208, 20, 44, 251, 83, 161, 173, 207, 75, 131, 234, 2, 17, 0, 0, 0, 2, 122, 156, 244, 199, 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