Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 986a63a7c29387940d359d8abd01be65c7fb68c5d07cc99f1fab85e65ff34e5a

Tx prefix hash: ffa80d388f1120898506b04fe401fb2fffac0fcb8fd3e9c4a0830ac69465b0b1
Tx public key: fcec1cc7e376e217a890a0df8f0ec6225c7f4651b1435ccbefd777e9db29da87
Timestamp: 1636913107 Timestamp [UCT]: 2021-11-14 18:05:07 Age [y:d:h:m:s]: 03:052:09:17:37
Block: 374263 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 816204 RingCT/type: yes/0
Extra: 01fcec1cc7e376e217a890a0df8f0ec6225c7f4651b1435ccbefd777e9db29da870211000000134a0f5013000000000000000000

1 output(s) for total of 35.311137263000 dcy

stealth address amount amount idx
00: 6250f2333a4d31963a7df67bf2257c62d6bf311a7ad12ccd7e818757b387d2ae 35.311137263000 757619 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": 374273, "vin": [ { "gen": { "height": 374263 } } ], "vout": [ { "amount": 35311137263, "target": { "key": "6250f2333a4d31963a7df67bf2257c62d6bf311a7ad12ccd7e818757b387d2ae" } } ], "extra": [ 1, 252, 236, 28, 199, 227, 118, 226, 23, 168, 144, 160, 223, 143, 14, 198, 34, 92, 127, 70, 81, 177, 67, 92, 203, 239, 215, 119, 233, 219, 41, 218, 135, 2, 17, 0, 0, 0, 19, 74, 15, 80, 19, 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