Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: ef533aadc10b96ce4429f20b961a7a490207dfb0366b71d2c29d49c4269e710f

Tx prefix hash: a2de76ddfec691de9e7837108a6dfccea2a3bb7e46cdac87914c9f080aab322f
Tx public key: db5c94d41ef0a0c6dbdee984f938726b9aa0e59cb1786f312a4c1bd6f1d47a6d
Timestamp: 1705796431 Timestamp [UCT]: 2024-01-21 00:20:31 Age [y:d:h:m:s]: 01:074:05:51:49
Block: 939768 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 314168 RingCT/type: yes/0
Extra: 01db5c94d41ef0a0c6dbdee984f938726b9aa0e59cb1786f312a4c1bd6f1d47a6d0211000000070011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: e98bf9ac859888ab4df2076e5371f2156acd0d1dfbbc1af75f151909e7053098 0.600000000000 1397898 of 15

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": 939778, "vin": [ { "gen": { "height": 939768 } } ], "vout": [ { "amount": 600000000, "target": { "key": "e98bf9ac859888ab4df2076e5371f2156acd0d1dfbbc1af75f151909e7053098" } } ], "extra": [ 1, 219, 92, 148, 212, 30, 240, 160, 198, 219, 222, 233, 132, 249, 56, 114, 107, 154, 160, 229, 156, 177, 120, 111, 49, 42, 76, 27, 214, 241, 212, 122, 109, 2, 17, 0, 0, 0, 7, 0, 17, 5, 91, 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