Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 65e4bb586f4b42eda6690b87f94485894d0d1d7263aad8d75e4685a42039cdb5

Tx prefix hash: 8732d9586df4c7c52bc67f3df692e68b0ff0277d5ecc15e5616265a2ee0061f8
Tx public key: ab1ffea2a0e8967c241d99f1e8d2db8b08cd9ac125dcc289bbbd6bece2b65308
Timestamp: 1702702482 Timestamp [UCT]: 2023-12-16 04:54:42 Age [y:d:h:m:s]: 01:150:20:21:42
Block: 914151 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 368969 RingCT/type: yes/0
Extra: 01ab1ffea2a0e8967c241d99f1e8d2db8b08cd9ac125dcc289bbbd6bece2b6530802110000000133af99f4000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: f233cdddd047d9e8ba0357a0990ac1863a9d0c3f8db1eb753929d141e5b5e0eb 0.600000000000 1371437 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": 914161, "vin": [ { "gen": { "height": 914151 } } ], "vout": [ { "amount": 600000000, "target": { "key": "f233cdddd047d9e8ba0357a0990ac1863a9d0c3f8db1eb753929d141e5b5e0eb" } } ], "extra": [ 1, 171, 31, 254, 162, 160, 232, 150, 124, 36, 29, 153, 241, 232, 210, 219, 139, 8, 205, 154, 193, 37, 220, 194, 137, 187, 189, 107, 236, 226, 182, 83, 8, 2, 17, 0, 0, 0, 1, 51, 175, 153, 244, 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