Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: d7bae043c101dbd70911585232c7c5180f1916774b8ac57f81f749a812be5efa

Tx prefix hash: 7316e2c7d0ee4e22c5f6ed780d975d581d4083be16f987f7bdc1627007e2c00f
Tx public key: 7943052824f65aac2cd0281d96fcf891c0ca3476b2909081d1014950e6a90314
Timestamp: 1608149538 Timestamp [UCT]: 2020-12-16 20:12:18 Age [y:d:h:m:s]: 04:080:12:40:59
Block: 163370 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1069908 RingCT/type: yes/0
Extra: 017943052824f65aac2cd0281d96fcf891c0ca3476b2909081d1014950e6a903140211000012ad4ea414e5000000000000000000

1 output(s) for total of 176.480033573000 dcy

stealth address amount amount idx
00: 2af302649b2f50719d810ae8e4ff1ea3fd5eb7d2099526d548d62b486f4238b5 176.480033573000 293067 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": 163380, "vin": [ { "gen": { "height": 163370 } } ], "vout": [ { "amount": 176480033573, "target": { "key": "2af302649b2f50719d810ae8e4ff1ea3fd5eb7d2099526d548d62b486f4238b5" } } ], "extra": [ 1, 121, 67, 5, 40, 36, 246, 90, 172, 44, 208, 40, 29, 150, 252, 248, 145, 192, 202, 52, 118, 178, 144, 144, 129, 209, 1, 73, 80, 230, 169, 3, 20, 2, 17, 0, 0, 18, 173, 78, 164, 20, 229, 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