Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: c6a2d4975149455fd14895d785b8bf168a61210f9d92aafc4309f169e5ec3f42

Tx prefix hash: 017be1dd0a126d0951c2290875ecdbe4264448f6ff342a0a6d9ea042ecab6077
Tx public key: cc7b05cc7d394037a92aebc0a923ad4922b980c5b08b50758b62f5a635eab467
Timestamp: 1707930790 Timestamp [UCT]: 2024-02-14 17:13:10 Age [y:d:h:m:s]: 00:260:07:30:09
Block: 957485 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 186398 RingCT/type: yes/0
Extra: 01cc7b05cc7d394037a92aebc0a923ad4922b980c5b08b50758b62f5a635eab4670211000000037a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 9c598723cadb503baabd5d152a594fb58d6395a6b6b4f15aa628f01d3c7a0823 0.600000000000 1416803 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": 957495, "vin": [ { "gen": { "height": 957485 } } ], "vout": [ { "amount": 600000000, "target": { "key": "9c598723cadb503baabd5d152a594fb58d6395a6b6b4f15aa628f01d3c7a0823" } } ], "extra": [ 1, 204, 123, 5, 204, 125, 57, 64, 55, 169, 42, 235, 192, 169, 35, 173, 73, 34, 185, 128, 197, 176, 139, 80, 117, 139, 98, 245, 166, 53, 234, 180, 103, 2, 17, 0, 0, 0, 3, 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