Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 0c69d1f5993264323a78b023e32e0b36572bc18545573b43609b695fc9ad3501

Tx prefix hash: e964dff6a024202cc2607fef8e5482cdae6d3b1ae165d2aa5e983995ac17b86e
Tx public key: be7ca93c73c3fe7346dfed1f80b99337b947d4c80e457bb2da2b32e2b2b92292
Timestamp: 1649574330 Timestamp [UCT]: 2022-04-10 07:05:30 Age [y:d:h:m:s]: 02:263:04:44:09
Block: 477110 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 707878 RingCT/type: yes/0
Extra: 01be7ca93c73c3fe7346dfed1f80b99337b947d4c80e457bb2da2b32e2b2b92292021100000001a8c141c5000000000000000000

1 output(s) for total of 16.111528774000 dcy

stealth address amount amount idx
00: 396d010642d852ed9e03f95a67ec45555483ef8c807e01cdf5022350af944b47 16.111528774000 897733 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": 477120, "vin": [ { "gen": { "height": 477110 } } ], "vout": [ { "amount": 16111528774, "target": { "key": "396d010642d852ed9e03f95a67ec45555483ef8c807e01cdf5022350af944b47" } } ], "extra": [ 1, 190, 124, 169, 60, 115, 195, 254, 115, 70, 223, 237, 31, 128, 185, 147, 55, 185, 71, 212, 200, 14, 69, 123, 178, 218, 43, 50, 226, 178, 185, 34, 146, 2, 17, 0, 0, 0, 1, 168, 193, 65, 197, 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