Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 2df05d3594321a129d37978b52ede9c3a4716e7decc6236a3585777fe254d07f

Tx prefix hash: 66b8011b6469cca4c5e040779358a3d406b84c3ac35572a19d08bf16b0ea1d2a
Tx public key: 2c51c6b2868d89a0507764a13d0bf818fd5c23085567ad701b78a2c1f47ac57d
Timestamp: 1578660935 Timestamp [UCT]: 2020-01-10 12:55:35 Age [y:d:h:m:s]: 04:325:05:45:01
Block: 42690 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1121768 RingCT/type: yes/0
Extra: 012c51c6b2868d89a0507764a13d0bf818fd5c23085567ad701b78a2c1f47ac57d0211000000c0b221b3d1000000000000000000

1 output(s) for total of 443.150406718000 dcy

stealth address amount amount idx
00: 47a6ac6eeb05c0ddaf7faba452e0023a24df139467fbd033302b83597d990b70 443.150406718000 77000 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": 42700, "vin": [ { "gen": { "height": 42690 } } ], "vout": [ { "amount": 443150406718, "target": { "key": "47a6ac6eeb05c0ddaf7faba452e0023a24df139467fbd033302b83597d990b70" } } ], "extra": [ 1, 44, 81, 198, 178, 134, 141, 137, 160, 80, 119, 100, 161, 61, 11, 248, 24, 253, 92, 35, 8, 85, 103, 173, 112, 27, 120, 162, 193, 244, 122, 197, 125, 2, 17, 0, 0, 0, 192, 178, 33, 179, 209, 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