Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 6dc8e6e12a7e038b8eab0f0ea4ad0e75182ea8d2fc1cb3744eb88c4423b34cd7

Tx prefix hash: 63192fa552c23bc89689399216b32d1e0d7c967eac6134d99af34212cd4eb1b9
Tx public key: e6b2deb42cc5a481460596400e570e1672cd20e7e50302125944fbf1d8b6954d
Timestamp: 1712422188 Timestamp [UCT]: 2024-04-06 16:49:48 Age [y:d:h:m:s]: 01:211:14:35:33
Block: 994699 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 409934 RingCT/type: yes/0
Extra: 01e6b2deb42cc5a481460596400e570e1672cd20e7e50302125944fbf1d8b6954d02110000000259dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 88a23eb28582ddb52db3f13a676616f542b00ee5005bda81e846f72cab2a9f89 0.600000000000 1455103 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": 994709, "vin": [ { "gen": { "height": 994699 } } ], "vout": [ { "amount": 600000000, "target": { "key": "88a23eb28582ddb52db3f13a676616f542b00ee5005bda81e846f72cab2a9f89" } } ], "extra": [ 1, 230, 178, 222, 180, 44, 197, 164, 129, 70, 5, 150, 64, 14, 87, 14, 22, 114, 205, 32, 231, 229, 3, 2, 18, 89, 68, 251, 241, 216, 182, 149, 77, 2, 17, 0, 0, 0, 2, 89, 218, 211, 245, 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