Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 11c1570d462b4e424dfc0e3379ea278cc62d740ab0662952e06c8502cd448e0c

Tx prefix hash: 9bff7d7c70b0062709b7e045861e1e78c637c5a74338f3f34e504eaa1de83471
Tx public key: e1e8db424d1e1109906f283f5955212389d24a7c4cdcd3e3a782acb62cc35470
Timestamp: 1728005369 Timestamp [UCT]: 2024-10-04 01:29:29 Age [y:d:h:m:s]: 00:055:10:26:10
Block: 1123926 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 39612 RingCT/type: yes/0
Extra: 01e1e8db424d1e1109906f283f5955212389d24a7c4cdcd3e3a782acb62cc3547002110000000191e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 30f5ba01b37a63649ecf7486b07019a3763fb2c1ec8a26672fb62ad00d3ec63e 0.600000000000 1606475 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": 1123936, "vin": [ { "gen": { "height": 1123926 } } ], "vout": [ { "amount": 600000000, "target": { "key": "30f5ba01b37a63649ecf7486b07019a3763fb2c1ec8a26672fb62ad00d3ec63e" } } ], "extra": [ 1, 225, 232, 219, 66, 77, 30, 17, 9, 144, 111, 40, 63, 89, 85, 33, 35, 137, 210, 74, 124, 76, 220, 211, 227, 167, 130, 172, 182, 44, 195, 84, 112, 2, 17, 0, 0, 0, 1, 145, 225, 60, 4, 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