Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 0e47b82d5e5f573ed9298121b3bc443767e20eeed8db480574bb9004bfc9a9eb

Tx prefix hash: d93a71c96dc8c26aa385eb206da7fc43769cf13f497a3922eca042e6656aec8c
Tx public key: afb965c076f972cd9f0ee4fbbc01f8a835ecec607ea34361adb6aa8012894650
Timestamp: 1583526277 Timestamp [UCT]: 2020-03-06 20:24:37 Age [y:d:h:m:s]: 04:363:00:26:23
Block: 77458 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1154026 RingCT/type: yes/0
Extra: 01afb965c076f972cd9f0ee4fbbc01f8a835ecec607ea34361adb6aa801289465002110000001c4943cd9f000000000000000000

1 output(s) for total of 339.899311851000 dcy

stealth address amount amount idx
00: f21bf255693835bc5bfd34fbb92cbb22e803a73a40e2e2d8113baae82393b0d3 339.899311851000 142593 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": 77468, "vin": [ { "gen": { "height": 77458 } } ], "vout": [ { "amount": 339899311851, "target": { "key": "f21bf255693835bc5bfd34fbb92cbb22e803a73a40e2e2d8113baae82393b0d3" } } ], "extra": [ 1, 175, 185, 101, 192, 118, 249, 114, 205, 159, 14, 228, 251, 188, 1, 248, 168, 53, 236, 236, 96, 126, 163, 67, 97, 173, 182, 170, 128, 18, 137, 70, 80, 2, 17, 0, 0, 0, 28, 73, 67, 205, 159, 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