Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 8a04782ff22d93f884615c705cd01bcef01950032835f0406c38682457649bb7

Tx prefix hash: 6ea4524e25ce8855c31ee202da74733a9c1f5fb6838b36fceb021ce21189bef2
Tx public key: 8fc63783a027d7747c5e33995116bfa0169bda4fd997c88cc4ed6d7f39d6b32e
Timestamp: 1617042303 Timestamp [UCT]: 2021-03-29 18:25:03 Age [y:d:h:m:s]: 03:273:21:52:20
Block: 229160 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 955239 RingCT/type: yes/0
Extra: 018fc63783a027d7747c5e33995116bfa0169bda4fd997c88cc4ed6d7f39d6b32e02110000002b3634f08d000000000000000000

1 output(s) for total of 106.833115748000 dcy

stealth address amount amount idx
00: b216e3aaed30a0510ec07c15b1f2cfd49a13dfdf22bf79ca33f95419e9157d48 106.833115748000 475440 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": 229170, "vin": [ { "gen": { "height": 229160 } } ], "vout": [ { "amount": 106833115748, "target": { "key": "b216e3aaed30a0510ec07c15b1f2cfd49a13dfdf22bf79ca33f95419e9157d48" } } ], "extra": [ 1, 143, 198, 55, 131, 160, 39, 215, 116, 124, 94, 51, 153, 81, 22, 191, 160, 22, 155, 218, 79, 217, 151, 200, 140, 196, 237, 109, 127, 57, 214, 179, 46, 2, 17, 0, 0, 0, 43, 54, 52, 240, 141, 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