Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 11807c2ccb9cb36fb8f2204af413e015afa35ab00777337087ce4c5a73a46ee2

Tx prefix hash: 4557811430ecfeaaf2ca2954e397146aafd88873b0b64aef3625586b0356c45c
Tx public key: e1a40a961cda01ef1b603b7a5c5db4b03846b02c559a01e8590b2a8b64593e53
Timestamp: 1742541610 Timestamp [UCT]: 2025-03-21 07:20:10 Age [y:d:h:m:s]: 00:244:11:38:10
Block: 1243978 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 172452 RingCT/type: yes/0
Extra: 01e1a40a961cda01ef1b603b7a5c5db4b03846b02c559a01e8590b2a8b64593e53021100000002ed95dce7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: d51defdcba07de1c0c1e490d388971022e9ae8912d9ca939614776b662b71b57 0.600000000000 1730969 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": 1243988, "vin": [ { "gen": { "height": 1243978 } } ], "vout": [ { "amount": 600000000, "target": { "key": "d51defdcba07de1c0c1e490d388971022e9ae8912d9ca939614776b662b71b57" } } ], "extra": [ 1, 225, 164, 10, 150, 28, 218, 1, 239, 27, 96, 59, 122, 92, 93, 180, 176, 56, 70, 176, 44, 85, 154, 1, 232, 89, 11, 42, 139, 100, 89, 62, 83, 2, 17, 0, 0, 0, 2, 237, 149, 220, 231, 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