Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 278367ab9833359c5e58a2de810d320867636a2d2d2290409cd049ba855e2c37

Tx prefix hash: d4e594f93f3e23b3258beaa2d4c8b332fec0887020a4ed70bf28481ca5121e94
Tx public key: 5de1e17168a0152d8751e94a06f100f12f10d8376a73095ae472d8df67eda17d
Timestamp: 1576643606 Timestamp [UCT]: 2019-12-18 04:33:26 Age [y:d:h:m:s]: 05:051:18:11:01
Block: 28310 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1184625 RingCT/type: yes/0
Extra: 015de1e17168a0152d8751e94a06f100f12f10d8376a73095ae472d8df67eda17d021100000026ad433a0b000000000000000000

1 output(s) for total of 494.536194662000 dcy

stealth address amount amount idx
00: fcc1f90a37c99cac5b32fd207ae049621cbd7ce076b5ce0d334eb4557b53e8d0 494.536194662000 46854 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": 28320, "vin": [ { "gen": { "height": 28310 } } ], "vout": [ { "amount": 494536194662, "target": { "key": "fcc1f90a37c99cac5b32fd207ae049621cbd7ce076b5ce0d334eb4557b53e8d0" } } ], "extra": [ 1, 93, 225, 225, 113, 104, 160, 21, 45, 135, 81, 233, 74, 6, 241, 0, 241, 47, 16, 216, 55, 106, 115, 9, 90, 228, 114, 216, 223, 103, 237, 161, 125, 2, 17, 0, 0, 0, 38, 173, 67, 58, 11, 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