Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a43c92ff1929accdc9bff9fc784cf687cbbfc996647c69081c9017f09742dff8

Tx prefix hash: 04973e476c52e0afcee3db962827c9e49346f5d4e74ce741c86171c13228ef34
Tx public key: c54556c7b062e81f33bae9b42af615d5cd04e5d3fbb4363c9134a6d64ad797cf
Timestamp: 1718538155 Timestamp [UCT]: 2024-06-16 11:42:35 Age [y:d:h:m:s]: 00:221:01:41:09
Block: 1045446 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 158147 RingCT/type: yes/0
Extra: 01c54556c7b062e81f33bae9b42af615d5cd04e5d3fbb4363c9134a6d64ad797cf0211000000017a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 2da196f0c0dd29cbccb48dbaaee7c4ce15aeea1e7174da62e532d4ae85832ca8 0.600000000000 1515021 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": 1045456, "vin": [ { "gen": { "height": 1045446 } } ], "vout": [ { "amount": 600000000, "target": { "key": "2da196f0c0dd29cbccb48dbaaee7c4ce15aeea1e7174da62e532d4ae85832ca8" } } ], "extra": [ 1, 197, 69, 86, 199, 176, 98, 232, 31, 51, 186, 233, 180, 42, 246, 21, 213, 205, 4, 229, 211, 251, 180, 54, 60, 145, 52, 166, 214, 74, 215, 151, 207, 2, 17, 0, 0, 0, 1, 122, 156, 244, 199, 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