Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 576e24106d3ebee4672fd363bc39a49e0289e06446fe76d0779ca02695c120ee

Tx prefix hash: b83ba17c2ef96f04f6f1202aaeed57534a8cdaada16430a310a089e80e831ca6
Tx public key: e3c37ab54d261aa1a88560883f3a41d7f77347e1a72bc01ca14c4fb17ce3badb
Timestamp: 1581510864 Timestamp [UCT]: 2020-02-12 12:34:24 Age [y:d:h:m:s]: 04:292:02:49:45
Block: 63373 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1100981 RingCT/type: yes/0
Extra: 01e3c37ab54d261aa1a88560883f3a41d7f77347e1a72bc01ca14c4fb17ce3badb021100000002c71d3ff9000000000000000000

1 output(s) for total of 378.481471289000 dcy

stealth address amount amount idx
00: d59ca69894e78e38196c55c0af088a6e44483074bca4a292fd322455ab9b76ed 378.481471289000 116877 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": 63383, "vin": [ { "gen": { "height": 63373 } } ], "vout": [ { "amount": 378481471289, "target": { "key": "d59ca69894e78e38196c55c0af088a6e44483074bca4a292fd322455ab9b76ed" } } ], "extra": [ 1, 227, 195, 122, 181, 77, 38, 26, 161, 168, 133, 96, 136, 63, 58, 65, 215, 247, 115, 71, 225, 167, 43, 192, 28, 161, 76, 79, 177, 124, 227, 186, 219, 2, 17, 0, 0, 0, 2, 199, 29, 63, 249, 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