Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 4ee3c37634c2374ae7258cf0dff0f32b2c15592e76e1f533f5efb71178d9988d

Tx prefix hash: bbd9f1aad2e5b4a38bc37ff51346dd1e8c1bd994947a0d57ed9579cab6aea277
Tx public key: d463369ee8cd55e31b264e84016e9e97d46944d470abc9dbdf5f5ecb49d7aab4
Timestamp: 1731778638 Timestamp [UCT]: 2024-11-16 17:37:18 Age [y:d:h:m:s]: 00:007:08:46:38
Block: 1155103 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 5290 RingCT/type: yes/0
Extra: 01d463369ee8cd55e31b264e84016e9e97d46944d470abc9dbdf5f5ecb49d7aab40211000000021f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 9f0d3384a6ba916dfce0116861af6ff92d81bd8d3d2899408379893a318134cf 0.600000000000 1640718 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": 1155113, "vin": [ { "gen": { "height": 1155103 } } ], "vout": [ { "amount": 600000000, "target": { "key": "9f0d3384a6ba916dfce0116861af6ff92d81bd8d3d2899408379893a318134cf" } } ], "extra": [ 1, 212, 99, 54, 158, 232, 205, 85, 227, 27, 38, 78, 132, 1, 110, 158, 151, 212, 105, 68, 212, 112, 171, 201, 219, 223, 95, 94, 203, 73, 215, 170, 180, 2, 17, 0, 0, 0, 2, 31, 10, 83, 235, 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