Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 3a13f179f21a33d97575367fc593969c5e74b386b591504e5df1da3a75c4f649

Tx prefix hash: eb44507d18bafab2d12779d9698ef877be37f58f0829d3a9eb515f35f898aaf4
Tx public key: 6202477eae510e5ba3676ee326ea4a21b0e6943fa2e119ec0fc8b4215627a411
Timestamp: 1693310089 Timestamp [UCT]: 2023-08-29 11:54:49 Age [y:d:h:m:s]: 01:184:22:42:17
Block: 836456 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 393283 RingCT/type: yes/0
Extra: 016202477eae510e5ba3676ee326ea4a21b0e6943fa2e119ec0fc8b4215627a41102110000000275e3f0e9000000000000000000

1 output(s) for total of 1.038661704000 dcy

stealth address amount amount idx
00: 64a27c44cff389faa355a7a03cf1cf56f76779ca882ee5df5bcf33f7afa6e471 1.038661704000 1289040 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": 836466, "vin": [ { "gen": { "height": 836456 } } ], "vout": [ { "amount": 1038661704, "target": { "key": "64a27c44cff389faa355a7a03cf1cf56f76779ca882ee5df5bcf33f7afa6e471" } } ], "extra": [ 1, 98, 2, 71, 126, 174, 81, 14, 91, 163, 103, 110, 227, 38, 234, 74, 33, 176, 230, 148, 63, 162, 225, 25, 236, 15, 200, 180, 33, 86, 39, 164, 17, 2, 17, 0, 0, 0, 2, 117, 227, 240, 233, 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