Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 893650717eae9563b8d1ed45bfe3c02ff7a064a7ce32725c54544b217a47a2ac

Tx prefix hash: e1a27feae53c41a878edb7ff21cf5e62ba420673e067187497cb7b30f1768893
Tx public key: 5cfcb5ad4614bbd9fd99e95477791c94f56f691bec05a42fa4e2e61b1088628c
Timestamp: 1727118637 Timestamp [UCT]: 2024-09-23 19:10:37 Age [y:d:h:m:s]: 00:108:18:30:46
Block: 1116567 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 77778 RingCT/type: yes/0
Extra: 015cfcb5ad4614bbd9fd99e95477791c94f56f691bec05a42fa4e2e61b1088628c021100000004e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 951f91b323d70c51757bea7837b9a5ef0ef0bc84fbee4152b6f9a5deeeb65538 0.600000000000 1597098 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": 1116577, "vin": [ { "gen": { "height": 1116567 } } ], "vout": [ { "amount": 600000000, "target": { "key": "951f91b323d70c51757bea7837b9a5ef0ef0bc84fbee4152b6f9a5deeeb65538" } } ], "extra": [ 1, 92, 252, 181, 173, 70, 20, 187, 217, 253, 153, 233, 84, 119, 121, 28, 148, 245, 111, 105, 27, 236, 5, 164, 47, 164, 226, 230, 27, 16, 136, 98, 140, 2, 17, 0, 0, 0, 4, 233, 20, 221, 21, 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