Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: cc43f1afed9755b4a70c5ba6cbb52d2393715ad5ef87ef1d84194036ec2c8c52

Tx prefix hash: 6e1ce9bc239e4353f1ac8b95c4dcfcb02716ae3ab77fd89335d0776881198424
Tx public key: 4cfa32b2a66ad68b0fbe7ef0fc0db473e2d37473e681d1f4ea2ec9ab074baacf
Timestamp: 1712218691 Timestamp [UCT]: 2024-04-04 08:18:11 Age [y:d:h:m:s]: 01:066:16:17:54
Block: 993013 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 308690 RingCT/type: yes/0
Extra: 014cfa32b2a66ad68b0fbe7ef0fc0db473e2d37473e681d1f4ea2ec9ab074baacf02110000000252d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 8dff5c3c9591109ece4ac7a15acb554719127a1a6323e7773ddaf590921d4c9e 0.600000000000 1453391 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": 993023, "vin": [ { "gen": { "height": 993013 } } ], "vout": [ { "amount": 600000000, "target": { "key": "8dff5c3c9591109ece4ac7a15acb554719127a1a6323e7773ddaf590921d4c9e" } } ], "extra": [ 1, 76, 250, 50, 178, 166, 106, 214, 139, 15, 190, 126, 240, 252, 13, 180, 115, 226, 211, 116, 115, 230, 129, 209, 244, 234, 46, 201, 171, 7, 75, 170, 207, 2, 17, 0, 0, 0, 2, 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