Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 030914b91f8b7fd9a3da9ced084fcc51264e3d94ae7a7b72c5dbaf972740b66c

Tx prefix hash: 86bf7a6b08d40a68f741ef93f69ad070a1ea8840d46164ed887d58a0536458c5
Tx public key: a6952f64e50070dceebaeff507e7ea7b15631c9c0e401336041196dc07a6eb68
Timestamp: 1583346335 Timestamp [UCT]: 2020-03-04 18:25:35 Age [y:d:h:m:s]: 04:268:22:17:33
Block: 76357 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1086599 RingCT/type: yes/0
Extra: 01a6952f64e50070dceebaeff507e7ea7b15631c9c0e401336041196dc07a6eb6802110000004156c366d3000000000000000000

1 output(s) for total of 342.766489797000 dcy

stealth address amount amount idx
00: dbb8603885a91ae12aa3b4caa308cdf8450710dbca053d3334c07c7fa06c558f 342.766489797000 140601 of 0

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": 76367, "vin": [ { "gen": { "height": 76357 } } ], "vout": [ { "amount": 342766489797, "target": { "key": "dbb8603885a91ae12aa3b4caa308cdf8450710dbca053d3334c07c7fa06c558f" } } ], "extra": [ 1, 166, 149, 47, 100, 229, 0, 112, 220, 238, 186, 239, 245, 7, 231, 234, 123, 21, 99, 28, 156, 14, 64, 19, 54, 4, 17, 150, 220, 7, 166, 235, 104, 2, 17, 0, 0, 0, 65, 86, 195, 102, 211, 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