Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f93cf72ce95a3a6e02094fc15e5dbffc6e0eab73bf5f40e17431b674f71ce809

Tx prefix hash: 2e826e62fcbce059e3861656ebdb4936043d84fb471ac486d3c0f124d61d5700
Tx public key: 7274a2467a9f9dff3a78819ce2e85280360f4c62f428be5e6ab027f72cabfd20
Timestamp: 1705648513 Timestamp [UCT]: 2024-01-19 07:15:13 Age [y:d:h:m:s]: 01:150:18:01:57
Block: 938550 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 368769 RingCT/type: yes/0
Extra: 017274a2467a9f9dff3a78819ce2e85280360f4c62f428be5e6ab027f72cabfd200211000000037a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: aa28d3c53a06815a19df4a76706de3970b0dc5899edf1ab0e8d0f32ceca07684 0.600000000000 1396620 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": 938560, "vin": [ { "gen": { "height": 938550 } } ], "vout": [ { "amount": 600000000, "target": { "key": "aa28d3c53a06815a19df4a76706de3970b0dc5899edf1ab0e8d0f32ceca07684" } } ], "extra": [ 1, 114, 116, 162, 70, 122, 159, 157, 255, 58, 120, 129, 156, 226, 232, 82, 128, 54, 15, 76, 98, 244, 40, 190, 94, 106, 176, 39, 247, 44, 171, 253, 32, 2, 17, 0, 0, 0, 3, 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