Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a3c310977ab22097458153962082691cd16513f418a158ed01709b7a3b7b7c66

Tx prefix hash: 3952e920057023c5e82957aa9e59e64b7024c8d6f311f107a56db3b4ec1e897d
Tx public key: dca0c9c959a82ed9570fdfe45b0fb1eb0ca6ba79087c4ecc696e06ae2e318a39
Timestamp: 1712786436 Timestamp [UCT]: 2024-04-10 22:00:36 Age [y:d:h:m:s]: 00:260:18:06:15
Block: 997729 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 186669 RingCT/type: yes/0
Extra: 01dca0c9c959a82ed9570fdfe45b0fb1eb0ca6ba79087c4ecc696e06ae2e318a390211000000080011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: a112d163af68271c0eee9cc57deab7cc360dd0ef1a70a222488fc2c9f29e1de7 0.600000000000 1458163 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": 997739, "vin": [ { "gen": { "height": 997729 } } ], "vout": [ { "amount": 600000000, "target": { "key": "a112d163af68271c0eee9cc57deab7cc360dd0ef1a70a222488fc2c9f29e1de7" } } ], "extra": [ 1, 220, 160, 201, 201, 89, 168, 46, 217, 87, 15, 223, 228, 91, 15, 177, 235, 12, 166, 186, 121, 8, 124, 78, 204, 105, 110, 6, 174, 46, 49, 138, 57, 2, 17, 0, 0, 0, 8, 0, 17, 5, 91, 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