Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 40ffbe29235eda1ef3d311a86cd1c7092be9eb21ce0f29c6b9834b277b7de58d

Tx prefix hash: e56e571686114121df3645e674b131f97bcb189518e7fe4f93dafbfc9e56027c
Tx public key: 8a7afd023bb3eae5c2a05ab770f8d1dd0d94a1036c0ca0f5f51e503203c35149
Timestamp: 1738594469 Timestamp [UCT]: 2025-02-03 14:54:29 Age [y:d:h:m:s]: 00:361:11:14:28
Block: 1211264 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 256038 RingCT/type: yes/0
Extra: 018a7afd023bb3eae5c2a05ab770f8d1dd0d94a1036c0ca0f5f51e503203c351490211000000071f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 31ea9bc88210e97cb1ac810ea23a50ce40fa6771111cda7407c35d0e7dd787a7 0.600000000000 1698023 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": 1211274, "vin": [ { "gen": { "height": 1211264 } } ], "vout": [ { "amount": 600000000, "target": { "key": "31ea9bc88210e97cb1ac810ea23a50ce40fa6771111cda7407c35d0e7dd787a7" } } ], "extra": [ 1, 138, 122, 253, 2, 59, 179, 234, 229, 194, 160, 90, 183, 112, 248, 209, 221, 13, 148, 161, 3, 108, 12, 160, 245, 245, 30, 80, 50, 3, 195, 81, 73, 2, 17, 0, 0, 0, 7, 31, 10, 83, 235, 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