Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: c727784e89fb453f608fb57ed4ef4dad3de479e017e43855fc037e4d86c842ee

Tx prefix hash: aceae6e3ba52e2e354e118ae67316663a2d547dc2a4ac0dff5b084dd7637ba56
Tx public key: 4c80c041f23430a417c0e49524db36ca45326e143d9954c0126b5c00e69b022e
Timestamp: 1710828202 Timestamp [UCT]: 2024-03-19 06:03:22 Age [y:d:h:m:s]: 01:029:05:41:14
Block: 981534 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 281865 RingCT/type: yes/0
Extra: 014c80c041f23430a417c0e49524db36ca45326e143d9954c0126b5c00e69b022e02110000000352d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 715c7bb3c58934b6daf57ea350d02f277bff2878b13c62b15feffa214cb57ab3 0.600000000000 1441631 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": 981544, "vin": [ { "gen": { "height": 981534 } } ], "vout": [ { "amount": 600000000, "target": { "key": "715c7bb3c58934b6daf57ea350d02f277bff2878b13c62b15feffa214cb57ab3" } } ], "extra": [ 1, 76, 128, 192, 65, 242, 52, 48, 164, 23, 192, 228, 149, 36, 219, 54, 202, 69, 50, 110, 20, 61, 153, 84, 192, 18, 107, 92, 0, 230, 155, 2, 46, 2, 17, 0, 0, 0, 3, 82, 212, 126, 148, 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