Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 692894bc001df26b1d705c7886b12acd68cdffe392b58753cbf4d5b4a277df10

Tx prefix hash: ae22b3a3df73098986ef54d0ee3c306b1c04be48c64d05b994054bca3c54bcb2
Tx public key: a572bdcd0a80461524d566878a6c9b07e1438fc9dc8b130b42426d6994162dcc
Timestamp: 1723553443 Timestamp [UCT]: 2024-08-13 12:50:43 Age [y:d:h:m:s]: 00:246:20:29:00
Block: 1087017 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 176309 RingCT/type: yes/0
Extra: 01a572bdcd0a80461524d566878a6c9b07e1438fc9dc8b130b42426d6994162dcc02110000000b91e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 543e57b32264bd4e9aea19bb77efe511ca2e5a95fdd4648517cffb1db05aaf68 0.600000000000 1561618 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": 1087027, "vin": [ { "gen": { "height": 1087017 } } ], "vout": [ { "amount": 600000000, "target": { "key": "543e57b32264bd4e9aea19bb77efe511ca2e5a95fdd4648517cffb1db05aaf68" } } ], "extra": [ 1, 165, 114, 189, 205, 10, 128, 70, 21, 36, 213, 102, 135, 138, 108, 155, 7, 225, 67, 143, 201, 220, 139, 19, 11, 66, 66, 109, 105, 148, 22, 45, 204, 2, 17, 0, 0, 0, 11, 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